1. Sales and Distribution Master Data EGN 5620 Enterprise Systems Configuration Fall, 2015

2. Sales & Distribution Master Data SAP Implementation

3. Business Process Integration
ECC 6.0
Business Process Integration
January 2008 FI SD MM
Transactions
Org Data
Master Data FI MM SD
Rules FI MM SD FI
In the Business Process Integration class we use the stool as a metaphor for the SAP structure. There are four basic components needed to run execute SAP. Three of these are the legs of the stool: org data, master data, and rules. These ‘hold up’ the transactions. Transactions cannot be run unless these are setup.
The legs are typically configured during the implementation process.
During BPI 1 we will setup the stool for Finance, Materials management and Sales and Distribution. MM SD
January 2008
© SAP AG - University Alliances and The Rushmore Group, LLC All rights reserved.
© SAP AG and The Rushmore Group, LLC 2008

4. Business Process Integration
ECC 6.0
Business Process Integration
January 2008 SD
Org Data
We are now ready to build master data for our sales and distribution functions SD
January 2008
© SAP AG - University Alliances and The Rushmore Group, LLC All rights reserved.
© SAP AG and The Rushmore Group, LLC 2008

5. ECC 6.0
Sales Organization
January 2008
A sales organization belongs to exactly one company code
A sales transaction is linked to only one Sales Organization
Functions of Sales Organization:
Sells and distributes products
Negotiates terms of sales
Responsible for these business transactions
SAP allows assigning one or more plants to a sales organization.
Legally, a sales organization is included in exactly one company code .
You can assign one or more plants to one sales organization.
The sales organization has an address.
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.
You can define your own sales document types within a sales organization.
You assign sales offices and your own employees to a sales organization.
All items in a sales & distribution document, that is, all items of an order, delivery or a billing document belong to a sales organization.
A sales organization is the highest summation level (after the organizational unit Client) for sales statistics with their own statistics currency.
The sales organization is used as a selection criterion for the lists of sales documents and for the delivery and billing due list.
For each sales organization, you can determine the printer for output differently based on sales and billing documents.
A sales organization cannot share any master data with other sales organizations. The master data must be created separately. The data for a distribution channel or a division can, however, be created for several distribution channels or divisions.
January 2008
© SAP AG - University Alliances and The Rushmore Group, LLC All rights reserved.
© SAP AG and The Rushmore Group, LLC 2008

6. Wholesale Distribution
ECC 6.0
January 2008
Distribution Channels
Distribution channels identify how products and services reach the customer
Distribution channels can be assigned to one or more Sales Organizations
Online Distribution
Channel (IN)
Wholesale Distribution
Channel (WH)
US Sales
UE##/UW##
These three make up a sales area.
Distribution Channel is attached to the Sales Org
Customer can exist in more than one sales area.
January 2008
© SAP AG - University Alliances and The Rushmore Group, LLC All rights reserved.
© SAP AG and The Rushmore Group, LLC 2008

7. Accessory Division (AS)
ECC 6.0
January 2008
Division
It can be assigned to one or more Sales Organizations
It is an organization level to which customer specific information and requirements are maintained (e.g. pricing, partial delivery)
It is often used to define product line distribution
Bicycle Division (BI)
Accessory Division (AS)
US Sales
UE##/UW##
A division can be directly attached to the Sales Org.
January 2008
© SAP AG - University Alliances and The Rushmore Group, LLC All rights reserved.
© SAP AG and The Rushmore Group, LLC 2008

8. Sales Area Sales Area comprised of:
ECC 6.0
Sales Area
January 2008
Sales Area comprised of:
Sales Organization
Distribution Channel
Division
Used to link together the organizational aspects of sales to customers
Also used for statistical analysis
SD is organized according to sales organization, distribution channel and division. A combination of these three organizational units forms the sales area.
These three make up a sales area.
Distribution Channel is attached to the Sales Org
Customer can exist in more than one sales area.
January 2008
© SAP AG - University Alliances and The Rushmore Group, LLC All rights reserved.
© SAP AG and The Rushmore Group, LLC 2008

9. Sales Area – (continued)
ECC 6.0
January 2008
Sales Area – (continued)
Online Dist
Channel (IN)
Wholesale Dist
Channel (WH)
US Sales
US##.UW##
Bicycle
Division
Accessory
These three make up a sales area.
Division is attached to the Distribution Channel which is attached to the Sales Org
Customer can exist in more than one sales area.
January 2008
© SAP AG - University Alliances and The Rushmore Group, LLC All rights reserved.
© SAP AG and The Rushmore Group, LLC 2008

10. Shipping and Loading Points
ECC 6.0
January 2008
Shipping and Loading Points
A shipping point is the top level in the organization for shipping
It usually exists physically in a plant
A shipping point can be allocated to several plants
It can be divided into several loading points (for more specialized handling)
A delivery is always initiated from exactly one shipping point. Thus all items of a delivery belong to one shipping point.
They usually exist physically in a plant
Each line item on an order is assigned to an order
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.
You can influence delivery scheduling via allocation to departure zones.
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.
You can determine the printer destination for messages differently for every shipping point on account of shipping documents.
In this step, you define the loading points for your company. The definition of loading points is optional, you can still use the SD system without defining loading points. A loading point has the following characteristics:
A loading point is a subdivision of a shipping point.
The loading point can be entered manually in the delivery header.
January 2008
© SAP AG - University Alliances and The Rushmore Group, LLC All rights reserved.
© SAP AG and The Rushmore Group, LLC 2008

11. Shipping Organization
ECC 6.0
January 2008
Shipping Organization
Plant
P_ _ _
Freight Dock
FD_ _ _
Express Dock
ED_ _ _
Rail Dock
RD_ _ _
Loading
Point 3
Point 2
Point 1
Point 4
Define it any way you want. It depends upon your organization.
In this example we have a plant
Assigned to the plant is a shipping point
Assigned to the shipping points are loading points.
January 2008
© SAP AG - University Alliances and The Rushmore Group, LLC All rights reserved.
© SAP AG and The Rushmore Group, LLC 2008

12. Business Process Integration
ECC 6.0
Business Process Integration
January 2008 SD
Master Data SD
We are now ready to build master data for our sales and distribution functions
Three elements of master data are the customer, material and pricing
© SAP AG and The Rushmore Group, LLC 2008

13. Master Data Core Elements - Customers
ECC 6.0
January 2008
Master Data Core Elements - Customers
Material
Customer
Pricing
Master Data
The three elements of master data are the customer, material and pricing. You set defaults in the master data to determine how the system will execute the transaction for these items.
January 2008
© SAP AG - University Alliances and The Rushmore Group, LLC All rights reserved.
© SAP AG and The Rushmore Group, LLC 2008

14. Customer Master Customer Master Data is created in Sales Area:
ECC 6.0
January 2008
Customer Master
Customer Master Data is created in Sales Area:
Sales Organization
Distribution Channel
Division
US Sales
UE##/UW##
Distribution
Channel – WH/IN
Division – BI/AS
Sales Area
Customer Master data is created by the sales area.
January 2008
© SAP AG - University Alliances and The Rushmore Group, LLC All rights reserved.
© SAP AG and The Rushmore Group, LLC 2008

15. Customer Master - (continued)
ECC 6.0
Customer Master - (continued)
January 2008
General Data:
Address
Sales Data:
Sales
Customer 43
1. General Data:
demographic data
2. Company Code Data:
Accounting information
3. Sales & Distribution Data:
Sales information
The customer master record is broken into three areas:
General Data: demographic data
Company Code Data: Financial Accounting – Accounting information
Sales Data – Sales information
General Data
General data does not depend on the company code, the sales and distribution organization or the purchasing organization. General data applies to one business partner for all company codes, and in all sales areas and purchasing organizations. It includes:
Company name
Address
Telephone number
General data is not limited to information used by both Financial Accounting and Logistics. The unloading point, for example, is unique for a customer and is only relevant for Sales and Distribution. However, because it is not part of the sales and distribution organization of your company, it is not sales and distribution data. It is general data.
If you edit a master record using the customer or vendor number without specifying a sales area, a purchasing organization, or a company code, the system displays only general data screens.
The department that creates the master record for a business partner also enters general data. If Financial Accounting creates the master record, it must also enter general data, such as the address. When Logistics then enters data, the general data for the business partner exists. Logistics can display the general data.
Company Code Data
Company code data only applies to one company code. This data is only relevant to Financial Accounting, and includes:
Account management data
Insurance data
If you edit a master record, you must specify the customer or vendor number and company code to access the screens containing company code data.
You can only invoice a business transaction if the data on the payer partner function is entered in the Financial Accounting view.
Sales and Distribution Data
The data for one customer can differ for each sales area. The sales area is a combination of sales organization, distribution channel and division. This data is only relevant to Sales and Distribution, and includes:
Pricing data
Delivery priority
Shipping conditions
If you edit a customer master record, you must enter the customer number and the sales area in order to access screens containing sales and distribution data.
You can only process sales and distribution transactions, for example, a sales order, after entering the sales and distribution data for a customer.
January 2008
© SAP AG - University Alliances and The Rushmore Group, LLC All rights reserved.
© SAP AG and The Rushmore Group, LLC 2008

16. ECC 6.0
Customer Master
January 2008
A master record must be created for every customer consisting of:
General data,
Company code data (Financial Accounting-FI), and
Sales & Distribution data (Sales and Distribution - SD)
Sales/distribution data
Sales
Shipping
Billing
Partner Usage
Company Code data
Account Mgmt
Payment
transactions
Correspondence
General data
Address
Control data
Vendor master has to be created for every vendor in the system
Data in vendor master records controls how transaction data is posted and processed for a vendor. The vendor master record also contains all the data you require to do business with your vendors.
The master record is used not only in Accounting but also in Materials Management. By storing vendor master data centrally and sharing it throughout your organization, you only need to enter it once. You can prevent inconsistencies in master data by maintaining it centrally. If one of your vendors changes their address, you only have to enter this change once, and your accounting and purchasing departments will always have up-to-date information.
A vendor master record contains:
Vendor’s name, address, language, and phone numbers
Tax numbers
Bank details
Account control data like the number of the G/L reconciliation account for the vendor account
Payment methods and terms of payment set up with the vendor
Purchasing data
January 2008
© SAP AG - University Alliances and The Rushmore Group, LLC All rights reserved.
© SAP AG and The Rushmore Group, LLC 2008

17. Customer Master 1. General Data – Address
ECC 6.0
January 2008
Customer Master 1. General Data – Address
General Data – Address
Address
Customer Name
Search Term
Street address
City, Region Postal code
Country
Communication
Language
Telephone, Fax,
Address
Name: Name of the customer.
Search Term: A method to find your customer by match-codes.
Street: Optional entry.
City: Mandatory entry.
Postal Code: Mandatory entry.
Country: Mandatory entry.
Communication
Language key Mandatory entry: This is the language the customer uses. All communications to them will be in this language
January 2008
© SAP AG - University Alliances and The Rushmore Group, LLC All rights reserved.
© SAP AG and The Rushmore Group, LLC 2008

18. Customer Master General Data – Control Data
ECC 6.0
January 2008
Customer Master General Data – Control Data
Account Control
Vendor
Authorization
Trading partner
Group key
Tax Information
Tax codes
Fiscal address
Country code
City code
Reference Data/Area
Account control
Vendor If the Customer is a Vendor as well, enter the Vendor number here. Account Number of Vendor or Creditor
Group key
If the customer or the vendor belongs to a group, you can enter a group key here. The group key is freely assignable.
If you create a matchcode using this group key, group evaluations are possible.
Authorization Group
The authorization group allows extended authorization protection for particular objects. The authorization groups are freely definable. The authorization groups usually occur in authorization objects together with an activity.
Tax information
Tax code 1 Number, with which the customer reports to the tax authorities.
Tax code 2 Number, with which the customer reports to the tax authorities.
Fiscal address Account number of the master record containing the fiscal address.
County code Key for county taxes.
City code Key is used for city taxes.
Tax jurisdiction code This code is used in the US to determine tax rates.
Reference data / area
Industry Freely definable name for a group of companies (e.g.trade, manufacturing).
Transport Zone Region, where the ship-to party is located.
International location number  (part 1)
Here you enter the first 7 digits of the international location number.
The International Location Number (ILN) is assigned (in Germany by the Centrale for Coorganisation GmbH)) when a company is founded. It consists of 13 digits, the last digit being the check digit. There are two categories of location numbers:
Participants who only need an ILN to cleary and unmistakably identify themselves for communication with the business partner are given a category 1 ILN. This cannot be used to identify articles by means of EAN.
Participants who wish to assign the location numbers for their own enterprise areas are given a category 2 ILN. For a category 2 ILN, digits 1 to 7 are described as basis number. This is used as basis for the creation of article numbers (EAN).
January 2008
© SAP AG - University Alliances and The Rushmore Group, LLC All rights reserved.
© SAP AG and The Rushmore Group, LLC 2008

19. Customer Master General Data – Payment Transactions
ECC 6.0
January 2008
Customer Master General Data – Payment Transactions
Bank Details
Country
Bank Key
Account holder
Bank Account
Control Key
Collection
EFT -
Country Country.
Bank Key Country-specific bank key. Normally, you manage banks using their bank number. The bank number in the control data for the bank is then displayed twice, that is, as the bank key too.
In certain countries, the bank account number takes on this function; then there are no bank numbers and the bank data is managed using the account number.
Account holder Name of account holder, if different from customer name.
Bank Account Number, under which the account is managed at the bank.
Control Key This field has different uses in different countries. In the US, this number is used to identify checking vs. savings account.
Collection This checkmark is selected, when the customer allows for direct payment collection through the bank.
January 2008
© SAP AG - University Alliances and The Rushmore Group, LLC All rights reserved.
© SAP AG and The Rushmore Group, LLC 2008

20. Customer Master 2. Company Code – Acct Information
ECC 6.0
January 2008
Customer Master 2. Company Code – Acct Information
Accounting Information
Reconciliation Account
Sort key
Head office
Interest Calculation
Interest indicator
Interest cycle
Interest calculation frequency in months
Last interest run
Reference Data
Previous account number
Buying group
Reconciliation Account Reconciliation account
Sort key This field indicates the standard sort sequence for the display of the line items.
Head office This field contains the account number of the head office.
Interest calculation
Interest indicator Checkmark for automatic interest calculation.
frequency Frequency of automatic interest calculation (in months).
Last key date System generated date of last interest calculation.
Reference data
Buying group Number of buying group (if applicable).
January 2008
© SAP AG - University Alliances and The Rushmore Group, LLC All rights reserved.
© SAP AG and The Rushmore Group, LLC 2008

21. Customer Master Company Code – Payment Transactions
ECC 6.0
January 2008
Customer Master Company Code – Payment Transactions
Payment Data
Terms of Payment
Tolerance group
Automatic Payment Transactions
Payment methods
Payment block
Alternative payer
Grouping key
Lockbox
Payment terms Payment terms including optional cash discount.
Tolerance group Freely definable group term for the business partner, customer and vendor, which determines the amount up to which payment differences are posted automatically to expense or revenue accounts when clearing items.
Record payment
history Indicator, which determines that the payment history of this customer is to be recorded.
Payment methods List of payment method(s) for automatic payments to this customer/vendor.
Alternative payer Account number for alternative payer, if bank collections are not to made via the customer’s account.
Lockbox Lockbox identification, to which customer is to make payments.
January 2008
© SAP AG - University Alliances and The Rushmore Group, LLC All rights reserved.
© SAP AG and The Rushmore Group, LLC 2008

22. Customer Master 3. Sales and Distribution – Sales
ECC 6.0
January 2008
Customer Master 3. Sales and Distribution – Sales
Sales Order
Sales District
Sales Office
Sales Group
Order Probability
Item Proposal
Pricing / Statistics
Price Group
Customer Pricing Procedure
Price List Type
Customer Statistical Group
Sales district Region where customer is located.
Sales office Your branch office or sales department that has responsibility for sales in a certain region
Sales group Sub section of a sales office. Group of sales people.
Order probability Statistical value based on the percentage set in the document type master record and the percentage set in the customer master record.
Item proposal Default value
Account at customer Account number, our company is listed under at customer.
Price group Grouping of customers for pricing purposes
Customer
pricing procedure Determines, together with other values, the pricing procedure for this customer.
Price list type Grouping of customers for pricing purposes
Customer statistical
group Indicates, which data will be updated in the Logistics Information System.
January 2008
© SAP AG - University Alliances and The Rushmore Group, LLC All rights reserved.
© SAP AG and The Rushmore Group, LLC 2008

23. Customer Master Sales and Distribution – Shipping
ECC 6.0
January 2008
Customer Master Sales and Distribution – Shipping
Shipping
Delivery Priority
Shipping Conditions
Delivering Plant
Order Combination
Partial Delivery
Complete Delivery Required By Law
Partial Delivery per Item
Max Part Deliveries
Under/Over delivery Tolerances
General Transportation Data
Transportation Zone
Delivery priority Allows deliveries to be processed based on different priorities.
Shipping conditions Determines, how the customer in general wants the goods to be shipped.
Delivering plant Plant, from which goods are (default) delivered to the customer.
Order combination Indicator, set when customer allows for different orders to be combined for delivery.
Partial delivery data
Complete delivery Indicator, set for customers, which don’t allow for partial deliveries to take place.
Maximum part deliveries Enter here the number of partial deliveries allowed by this customer. (Maximum 9).
General transportation data
Transport zone Location zone of ship-to party
Route determination = shipping conditions + transportation group + transportation zone
Transportation time defined per Route in IMG
January 2008
© SAP AG - University Alliances and The Rushmore Group, LLC All rights reserved.
© SAP AG and The Rushmore Group, LLC 2008

24. Customer Master Sales and Distribution – Billing
ECC 6.0
January 2008
Customer Master Sales and Distribution – Billing
Billing Section
Subs. Invoice Processing
Rebate
Price Determination
Invoicing Dates
Delivery and Payment Terms
Incoterms
Payment Terms
Accounting
Account Assignment Group
Taxes
Tax Classification
Billing section
Manual invoice
maintenance Indicates, if invoice should be printed for further manual processing.
Rebate Indicates, if customer is eligible for rebates.
Billing schedule Identifies the calendar, which determines the billing schedule for this customer.
Delivery and payment terms
Incoterms 1 Assigns transportation responsibilities and ownership transfer.
Incoterms 2 Additional information.
Payment terms Payment terms including optional cash discount.
Accounting
Account assignment
group Determines the revenue accounts for this customer’s sales transactions.
Tax data
Country Country
Tax category Taxes, applicable to this material
Tax classification taxable or exempt
January 2008
© SAP AG - University Alliances and The Rushmore Group, LLC All rights reserved.
© SAP AG and The Rushmore Group, LLC 2008

25. Customer Master Sales and Distribution – Partner Functions
ECC 6.0
January 2008
Customer Master Sales and Distribution – Partner Functions
Partner Functions
Partner Function (PF)
Number
Partner Description
Partial list of Partner Functions Types
SP – Sold-to-party
BP – Bill-to-party
PY – Payer
SH – Ship-to-party
Partner function
The abbreviated form of the name that identifies the partner function.
Number :Number of an SD business partner
Customer description of partner (plant, storage location)
Use
Sold-to party number sent in by the customer in delivery schedules.
The system uses this number to automatically determine the ship-to party.
January 2008
© SAP AG - University Alliances and The Rushmore Group, LLC All rights reserved.
© SAP AG and The Rushmore Group, LLC 2008

26. Business Partners Sold-to Party
ECC 6.0
January 2008
Business Partners Sold-to Party
Customer who orders can default for all partner functions — sold-to, ship-to, payer, bill-to
Primary type of business partner
Independent and cannot be linked to other sold-to partners
Sold-to
Ship-to
Bill-to
Payer
Customer who orders
Can default for all partner functions — sold-to, ship-to, payer, bill-to
Primary type of business partner
Independent and cannot be linked to other sold-to partners
January 2008
© SAP AG - University Alliances and The Rushmore Group, LLC All rights reserved.
© SAP AG and The Rushmore Group, LLC 2008

27. Business Partners Ship-to Party
ECC 6.0
January 2008
Business Partners Ship-to Party
Receive delivery
Can be linked to more than one sold-to address
Sold-to
Ship-to
Bill-to
Payer
Receive delivery
Can be linked to more than one sold-to address
A sold-to can have multiple ship-to’s
January 2008
© SAP AG - University Alliances and The Rushmore Group, LLC All rights reserved.
© SAP AG and The Rushmore Group, LLC 2008

28. Business Partners Bill-to Party
ECC 6.0
January 2008
Business Partners Bill-to Party
Sold-to
Ship-to
Bill-to
Payer
Partner who is delivered the invoice
Can be linked to more than one sold-to address
Partner who is delivered the invoice
Can be linked to more than one sold-to address
A sold to can have multiple bill-to’s
January 2008
© SAP AG - University Alliances and The Rushmore Group, LLC All rights reserved.
© SAP AG and The Rushmore Group, LLC 2008

29. Business Partners Payer
ECC 6.0
January 2008
Business Partners Payer
Sold-to
Ship-to
Bill-to
Payer
Partner who pays the bill
Can be linked to more than one sold-to address
Partner who pays the bill
Can be linked to more than one sold-to address
January 2008
© SAP AG - University Alliances and The Rushmore Group, LLC All rights reserved.
© SAP AG and The Rushmore Group, LLC 2008

30. Single and Multiple Ship-to Parties
ECC 6.0
January 2008
Single and Multiple Ship-to Parties
Payer: 10
Bill-to: 10
Ship-to: 10
Sold-to: 10
Single ship-to
Multiple ship-to’s
Single payer
Payer: 10
Bill-to: 10
Ship-to: 10
Sold-to: 10
Ship-to: 11
Here are two examples of ship to.
The first is a single sold-to and a single ship-to
The seconds is a single sold-to and two ship-to’s
January 2008
© SAP AG - University Alliances and The Rushmore Group, LLC All rights reserved.
© SAP AG and The Rushmore Group, LLC 2008

31. Business Partners Sold-to Bill-to Payer Ship-to ECC 6.0 January 2008
Here is just an example of a possible business partner with multiple ship-to’s a single payer and a single bill-to.
January 2008
© SAP AG - University Alliances and The Rushmore Group, LLC All rights reserved.
© SAP AG and The Rushmore Group, LLC 2008

32. Master Data Core Elements - Pricing
ECC 6.0
January 2008
Master Data Core Elements - Pricing
Material
Customer
Pricing
Master Data
The three elements of master data are the customer, material and pricing. You set defaults in the master data to determine how the system will execute the transaction for these items.
January 2008
© SAP AG - University Alliances and The Rushmore Group, LLC All rights reserved.
© SAP AG and The Rushmore Group, LLC 2008

33. Standard Pricing Process
ECC 6.0
Standard Pricing Process
January 2008
Standard Pricing
Calculates the gross price
Then applies
Discounts
Surcharges
Applicable Taxes
Calculates the final price
Final price = gross price - discounts + surcharges + taxes
The standard pricing process is as follows:
A standard or gross prices first calculated, or determined from the tables
Any applicable discount, surcharge or tax is determined and adjusted from the gross price. There may be more than one adjustment and the adjustments may be amounts, percentages, or other.
The final price is then calculated.
January 2008
© SAP AG - University Alliances and The Rushmore Group, LLC All rights reserved.
© SAP AG and The Rushmore Group, LLC 2008

34. Cost-Plus Pricing Process
ECC 6.0
Cost-Plus Pricing Process
January 2008
Cost-plus pricing
Captures the base cost
Then applies
Markup
Discounts
Surcharges
Applicable Taxes
Calculates the final price
Final price = cost + markup - discounts + surcharges + taxes
You can set price min’s and max’s on the header and line item
Margin control can be turned on
The cost plus pricing process is not very much different than the standard pricing process except we work from the bottom up instead of the top down.
First, the cost of the material is determined
Then an additional markup is added (margins)
Any applicable discount, surcharge or tax is determined and adjusted from the adjusted margin price. There may be more than one adjustment and the adjustments may be amounts, percentages, or other.
From this the final price is determined.
January 2008
© SAP AG - University Alliances and The Rushmore Group, LLC All rights reserved.
© SAP AG and The Rushmore Group, LLC 2008

35. ECC 6.0
Pricing Procedure
January 2008
Pricing procedures are assigned to the transactions for sale order process by defining the following dependencies:
Customer
Sales Document Type
Sales area
The pricing procedure will then apply
Prices (Gross)
Discounts & Surcharges
Freight
Taxes
First by line item
Then header - order type
You assign the pricing procedures to the transactions by defining the following dependencies:
Customer
Sales Document Type
Sales area
In the pricing procedure, you 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.
The determination of the procedure depends on the following factors:
Customer determination procedure
You specify the customer determination procedure in the customer master record for each sales area.
Document pricing procedure
You specify the document pricing procedure for each sales document type and billing type.
To determine the procedure, you allocate the customer determination procedure and the document pricing procedure to a pricing procedure within a sales area.
The primary job of a pricing procedure is to define a group of condition types in a particular sequence. The pricing procedure also determines:
Which sub-totals appear during pricing
To what extent pricing can be processed manually
Which method the system uses to calculate percentage discounts and surcharges
Which requirements for a particular condition type must be fulfilled before the system takes the condition into account
conditions:
Prices
Surcharges and Discounts
Freight Costs
Sales Taxes
These are:
Percent discount
Absolute discount
Freight
Order value
Material discount
Customer/Material
Customer discount
Material price
January 2008
© SAP AG - University Alliances and The Rushmore Group, LLC All rights reserved.
© SAP AG and The Rushmore Group, LLC 2008

36. Pricing Procedure – (continued)
ECC 6.0
Pricing Procedure – (continued)
January 2008
The sequence of activities for pricing process:
Define pricing procedure based on sales area, sales document, and customer (e.x. RVAJUS).
Define condition types (e.x. PR00) for each of the price elements, such as prices, discounts, and surcharges.
Define the access sequences (e.x. PR02) that enable the system to find valid condition records.
Searching for price according to a provided access sequence
The standard R/3 System includes predefined elements for routine pricing activities. For example, the standard system includes condition types for basic pricing elements, such as material prices, customer and material discounts, and surcharges such as freight and sales taxes. In the case of each element, you can use the standard version, modify the standard version, or create entirely new definitions to suit your own business needs. The sequence of activities is generally as follows:
Define condition types for each of the price elements (prices, discounts, and surcharges) that occur in your daily business transactions.
Define the condition tables that enable you to store and retrieve condition records for each of the different condition types.
Define the access sequences that enable the system to find valid condition records.
Group condition types and establish their sequence in pricing procedures.
pricing procedures : You assign the pricing procedures to the transactions by defining the following dependencies:
Customer
Sales document type
Sales area
In the pricing procedure, you 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.
The determination of the procedure depends on the following factors:
Customer determination procedure
You specify the customer determination procedure in the customer master record for each sales area.
Document pricing procedure
You specify the document pricing procedure for each sales document type and billing type.
To determine the procedure, you allocate the customer determination procedure and the document pricing procedure to a pricing procedure within a sales area.
You can make prices, surcharges, and discounts dependent on almost all the fields in a document. You define these dependencies using the condition tables. 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.
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.
January 2008
© SAP AG - University Alliances and The Rushmore Group, LLC All rights reserved.
© SAP AG and The Rushmore Group, LLC 2008

37. Pricing Process Select a line Item in Sales Order EPAD10## Sales Area
ECC 6.0
Pricing Process
January 2008
Select a line Item in
Sales Order
EPAD10##
Sales Area
SE##-WH-AS
Doc. Pric.
Proc. A
Cus. Pric. 1
Determine a
Pricing Procedure
Pricing Procedure = RVAJUS
Pricing Procedure
Contains List of
Condition Types
Condition Type PR00
Access Sequence PR02
10 – Customer/material
20 – Price list cat./currency/material
30 – Material
Condition Types
Point to
Access Sequence
The pricing procedure is used for each line item in the order.
The system determines the pricing procedure according to information defined in the sales document type and the customer master record.
The pricing procedure defines the valid condition types and the sequence in which they appear in the sales order. In the example, the system takes the first condition type (PR00) in the pricing procedure and begins the search for a valid condition record.
Each condition type in the pricing procedure can have an access sequence assigned to it. In this case, the system uses access sequence PR00. The system checks the accesses until it finds a valid condition record. (Although you cannot see this in the diagram, each access specifies a particular condition table. The table provides the key with which the system searches for records).
In the example, the first access (searching for a customer-specific material price) is unsuccessful. The system moves on to the next access and finds a valid record.
The system determines the price according to information stored in the condition record. If a pricing scale exists, the system calculates the appropriate price. In the example, the sales order item is for the material. Using the scale price that applies to quantities of USD 9.50 per piece.
Access Sequence
Provides the Search
Order for Pricing
30 – Material Price = $75
January 2008
© SAP AG - University Alliances and The Rushmore Group, LLC All rights reserved.
© SAP AG and The Rushmore Group, LLC 2008

38. Credit Limits and Checking
ECC 6.0
January 2008
Credit Limits and Checking
Define automatic credit limit checks to your company’s requirements
You can also define at what point the system carries out these checks (order, delivery, goods issue, and so on)
A credit representative is automatically alerted to a customer’s critical credit situation as soon as order processing starts
Employees can be automatically notified of critical credit situations via internal mail
Credit Management includes the following features:
Depending on your credit management needs, you can specify your own automatic credit checks based on a variety of criteria. You can also specify at which critical points in the sales and distribution cycle (for example, order entry, delivery, goods issue) the system carries out these checks.
During order processing, the credit representative automatically receives information about a customer’s critical credit situation.
Critical credit situations can also be automatically communicated to credit management personnel through internal electronic mail.
Your credit representatives are in a position to review the credit situation of a customer quickly and accurately and, according to your credit policy, decide whether or not to extend credit.
You can also work with Credit Management in distributed systems; for example if you were using centralized Financial Accounting and decentralized SD on several sales computers.
January 2008
© SAP AG - University Alliances and The Rushmore Group, LLC All rights reserved.
© SAP AG and The Rushmore Group, LLC 2008

39. Master Data Core Elements - Material
ECC 6.0
January 2008
Master Data Core Elements - Material
Material
Customer
Pricing
Master Data
The three elements of master data are the customer, material and pricing. You set defaults in the master data to determine how the system will execute the transaction for these items.
January 2008
© SAP AG - University Alliances and The Rushmore Group, LLC All rights reserved.
© SAP AG and The Rushmore Group, LLC 2008

40. Material Master – Sales Views (review)
ECC 6.0
Material Master – Sales Views (review)
January 2008
Sales: sales org. 1
Sales: sales org 2
Sales: general/plant
Foreign trade export
Sales: text
Sales Org. 1
View
Sales Org. 2
Barrel Pen
Once you create a view, you can only change a view. You cannot delete it.
The views determine how an material master record will be created.
January 2008
© SAP AG - University Alliances and The Rushmore Group, LLC All rights reserved.
© SAP AG and The Rushmore Group, LLC 2008

41. Business Rules SD Rules ECC 6.0 January 2008
© SAP AG - University Alliances and The Rushmore Group, LLC All rights reserved.
© SAP AG and The Rushmore Group, LLC 2008

42. ECC 6.0
Availability Check
January 2008
For determining the material availability date, SAP can include specific stocks below, if selected:
Inventory reserved for safety stock
Stock in transfer
Quality inspection stock
Blocked stock
Restricted use stock
All movements of stock
The following elements can be included in the availability check:
Stock
safety stock
stock in transfer
quality inspection
blocked stock
Inward/Outward movement of goods
purchase orders
purchase requisitions
planned orders
production orders
reservations
dependent reservations
dependent requirements
sales requirements
delivery requirements
Requirements in sales and distribution (sales requirements and delivery requirements) result from all transactions which forward a requirement to Materials Management (MM) or to Production Planning (PP). For example, this could include sales orders or deliveries and quotations as well. Sales and distribution requirements reduce existing stock or inward movements of stock on the material availability date to ensure that other outward movement of stock elements cannot access the quantity reserved in this way.
January 2008
© SAP AG - University Alliances and The Rushmore Group, LLC All rights reserved.
© SAP AG and The Rushmore Group, LLC 2008

43. Shipping Functions Shipping Point Determination
ECC 6.0
Shipping Functions
January 2008
Shipping Point Determination
The shipping point is selected for each line item based on the shipping point determination process
Shipping point selection is based on:
Shipping condition
Loading group
Delivering plant
Shipping points are independent organizational entities within which processing and monitoring of the deliveries as well as goods issue is carried out. A delivery is processed by one shipping point only.
A shipping point can be determined for each order item. How the shipping point is determined depends on three factors:
The shipping conditions from the customer master record (Shipping screen)
For example, it might have been agreed with the customer that the goods are to be delivered as soon as possible.
The loading group from the material master record (Sales/Plant Data screen)
You could, for example, specify a loading group that defines that the goods must always be loaded with a crane or a forklift.
The delivering plant
This plant is determined per order item either from the customer master record or from the material master record. However, you can also enter it manually for each order item.
January 2008
© SAP AG - University Alliances and The Rushmore Group, LLC All rights reserved.
© SAP AG and The Rushmore Group, LLC 2008

44. Shipping Functions Route Definition Route Determination
ECC 6.0
January 2008
Shipping Functions
Route Definition
Define delivery method and the transit time
‘Dummy’ routes can be used to easily define transit time
Route Determination
Proposed route is chosen using
Shipping point
Destination country
Transportation zone
Shipping condition
The route determines the means of transport and the legs involved. It influences transportation scheduling. For example, the system can determine from the route that goods are to be sent by rail to Boston. Therefore, during transportation scheduling, it takes into account how far in advance loading space in the freight car must be reserved.
Criteria for Route Proposal in the Sales Order
A route can be determined for every order item. Determining the route in the sales order depends on the following factors:
Country and departure zone of the shipping point
Shipping condition from the sales order
For example, it might have been agreed with the customer that the goods are to be delivered as soon as possible.
Transportation group from the material master record (Sales/Plant Data screen)
You can use the transportation group to group together goods with the same characteristics (for example, bulky goods or goods that must be transported in refrigerated trucks).
Country and transportation zone of the ship-to party (Control screen in the customer master record)
January 2008
© SAP AG - University Alliances and The Rushmore Group, LLC All rights reserved.
© SAP AG and The Rushmore Group, LLC 2008

45. Sales & Distribution
Master Data
GBI, Inc.

46. Enterprise Structure Client (330) Credit Control Fiscal Year
Plants
(DL##/MI##/SD##)
Client (330)
Chart of
Accounts (GL##)
Company
Code (US##)
Fiscal Year
Variant (K1)
Credit Control
Area (GL##)
Purchasing
Org. (US ##)
Group (N##)
Shipping Point (DL##/MI##/SD##)
Distribution
Channel (IN/WH)
Division (BI/AS)
Sales Area
Controlling Area (NA ##)
FG##
SF##
Sales
Org. (UE##/UW##)
Business Area (BI##)
Cost centers
RM##
MI##
TG##

47. GBI Customers

48. Customer Master General & Company Code Data:

49. Customer Master Sales Area Data:

50. Customer Master Price Data:
Discount for specific customer:

51. Customer Master Credit Data:

52. Assign Sales Areas to Price Procedures:
To link sales area to a pricing procedure. The RVAJUS pricing procedure is the standard USA pricing procedure with jurisdiction code.
In the pricing procedure, prices are assigned to individual line items in sales order as well as discounts, surcharges, etc.
SOrg.
DChl Dv
DoPr
CuPP
PriPr.
UE## WH AS A 1
RVAJUS BI
UW## IN

53. Exercises: (Due date 9/12/2015)
1. Define Sales Organization
2. Define Shipping Point
3. Assign Sales Organization to Comp. Code
4. Assign Distribution Channel to Sales Org
5. Assign Division to Sales Organization
6. Set Up Sales Area
7. Assign SO – Distribution Channel – Plant
8. Assign Sales Area to Credit Control Area
9. Assign Business Area to Plant and Div
10. Assign Shipping Point to Plant
11. Assign SP with Loading Groups
12. Assign G/L Revenue Accounts
13. Define Pricing Procedure Determination
14: Define Rules by Sales Area

54. Exercises: (Due date 3/16/2015)
15. Extend Material Master
16. Create Customers
17. Create Pricing Conditions
18. Create Customer Specific Material Price
19. Create Customer Discount
20. Establish Credit Limit for Customers