1. Sales and Distribution Master Data EGN Enterprise Systems Configuration (Professional MSEM) Fall, 2012

2. Sales & Operations Planning (SOP) Overview
Sales and Operations Planning (SOP) covers various activities including the specification of medium term and long term sales volumes and the approximate planning of the production activities that are required to meet these volumes.
SOP can be done at the level of finished products or using product groups. Any combinations of materials or even of product groups themselves can be grouped together into other product groups.

3. Sales Planning - result
ECC 6.0
January 2008
Sales Planning - result
Sales planning results in creating the demand program as an input for production plan
Demand program feeds the production plan with the following data elements:
Time Buckets
Sales
Production
Stock levels
Days supply
January 2008
© SAP AG - University Alliances and The Rushmore Group, LLC All rights reserved.
© SAP AG and The Rushmore Group, LLC 2008

4. Sales & Distribution Master Data SAP Implementation EGN Enterprise Systems Configuration (Professional MSEM) Fall, 2012

5. 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

6. 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

7. 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
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.
It allows assigning sales offices and employees to the 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

8. Wholesale Distribution
ECC 6.0
January 2008
Distribution Channel
It can be assigned to one or more Sales Organizations
It identifies how products and services reach the customer
Retail Distribution
Channel (RE)
Wholesale Distribution
Channel (WH)
US Sales
S_ _ _
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. Division It can be assigned to one or more Sales Organizations
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
Medical Division
Chemical Division
US Sales
S _ _ _
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

10. 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

11. Sales Area – (continued)
ECC 6.0
January 2008
Sales Area – (continued)
Retail Dist
Channel (RE)
Wholesale Dist
Channel (WH)
US Sales
S_ _ _
Medical
Division
Chemical
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

12. Internal Sales Organization
ECC 6.0
January 2008
Internal Sales Organization
Typically defines a territory or market
Linked to one or more Sales Areas
A reference sales organization structure:
Sales Offices
Sales Groups
Sales Persons
Sales Office
The organization in Sales is represented by the elements sales office, sales group and salespersons.
Eastern Sales
Western Sales
US Sales
S_ _ _
January 2008
© SAP AG - University Alliances and The Rushmore Group, LLC All rights reserved.
© SAP AG and The Rushmore Group, LLC 2008

13. Sales Group & Sales Persons
ECC 6.0
Sales Group & Sales Persons
January 2008
Sales Group
Sub-division of a sales office, territory or market
Sales Person
Defined in Human Resources (HR) — Personnel Admin.
Specifically defines an individual rather than a position (sales rep.) in sales processing
The staff of a sales office may be subdivided into sales groups. For example, sales groups can be defined for individual divisions.
January 2008
© SAP AG - University Alliances and The Rushmore Group, LLC All rights reserved.
© SAP AG and The Rushmore Group, LLC 2008

14. Internal Sales Organization
ECC 6.0
Internal Sales Organization
January 2008
Eastern Sales
(Office)
Western Sales
US Sales
S_ _ _
Northeast
Sales Group
Southeast
Northwest
Southwest
Salesperson 1 4 3 6 5 8 7 2
The organization in Sales is represented by the elements sales office, sales group and salespersons
January 2008
© SAP AG - University Alliances and The Rushmore Group, LLC All rights reserved.
© SAP AG and The Rushmore Group, LLC 2008

15. 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 shopping 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

16. 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

17. 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
January 2008
© SAP AG - University Alliances and The Rushmore Group, LLC All rights reserved.
© SAP AG and The Rushmore Group, LLC 2008

18. 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

19. 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
S _ _ _
Distribution
Channel - RE
Division - 01
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

20. Customer Master - (continued)
ECC 6.0
Customer Master - (continued)
January 2008
General Data:
Address
Sales Data:
Sales
Customer 43
General Data:
demographic data
Company Code Data:
Accounting information
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

21. 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

22. Customer Master General Data – Address
ECC 6.0
January 2008
Customer Master 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

23. 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

24. 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

25. Customer Master General Data – Marketing
ECC 6.0
January 2008
Customer Master General Data – Marketing
Classification
Nielsen ID
Customer classification
Industry
Industry codes
Operating Figures
Annual sales
Number of employees
Fiscal year variant
Sales Prospecting
Legal status
Nielsen ID Nielsen indicator. The regional division of the company according to the Nielsen Institute, allows market analysis of your market by the A.C. Nielsen Company.
Customer
classification Freely definable customer classification field.
Industry Branch of industry classification of customer.
Industry code 1 Standard Industry Codes (SIC).
Operating figures
Annual sales Annual sales in currency in year.
Number of employees Number of employees in year.
Fiscal year variant The fiscal year variant of the company.
Sales prospecting
Legal status A coding of the legal status of the company i.e. Limited, Incorporated. There may be restrictions based upon the legal status of an organization. For example, you may not be able to buy a state employee lunch or dinner while prospecting.
January 2008
© SAP AG - University Alliances and The Rushmore Group, LLC All rights reserved.
© SAP AG and The Rushmore Group, LLC 2008

26. Customer Master General Data – Unloading Point
ECC 6.0
January 2008
Customer Master General Data – Unloading Point
Unloading Points
Unloading point
Default
Calendar key
Default Unloading Point
Goods receiving hours
Unloading point The customer point at which deliveries are to be unloaded.
Customer calendar Defines the factory calendar that your customer uses, specifying days on which deliveries will be accepted.
Unloading point default If more than one unloading point is specified, this check box is used to identify which unloading point is to be defaulted.
Goods receiving hours Customer specific schedule of receiving hours.
January 2008
© SAP AG - University Alliances and The Rushmore Group, LLC All rights reserved.
© SAP AG and The Rushmore Group, LLC 2008

27. Customer Master General Data – Foreign Trade
ECC 6.0
January 2008
Customer Master General Data – Foreign Trade
Export Data
Country key
TDO Date (Table of Denial Orders)
SDN Date (Specially Designated Nationals)
Boycott Date
Usage
Mainly civilian usage
Mainly military usage
Classification
Biochemical warfare
Nuclear nonproliferation
National security
SAP keeps up to date and send patches/updates all the time.
Country key for export Country key for the country that placed this customer on the boycott list.
control of customer
Table of Denial Orders Check mark indicator for customer who is listed in the Table of Denial Orders list. (US)
list (TDO)
TDO date Date, on which the customer was last checked on the TDO list.
Special Designated List of individuals and companies that US companies shouldn’t trade with or only on a limited basis.
Nationals list (SDN)
SDN date Last check date for customer on SDN list
Boycott Check mark for customers on your company’s boycott list.
Boycott date Date, on which the customer was last checked on the company boycott list.
Mainly civilian usage Indicators for customer’s product usage.
Mainly military usage Indicators for customer’s product usage.
Classification Indicators for: Chemical/Biological Warfare, Nuclear Nonproliferation, National security and Missile technology.
January 2008
© SAP AG - University Alliances and The Rushmore Group, LLC All rights reserved.
© SAP AG and The Rushmore Group, LLC 2008

28. Customer Master General Data – Contact Persons
ECC 6.0
January 2008
Customer Master General Data – Contact Persons
Contact Person
Name
First name
Department
Function
Name Name of contact.
Telephone1 First telephone number of the contact.
Department Description of the department of the contact for internal purposes.
First name First name of contact
Form of address e.g. Mr., Ms.
Function Job function of contact.
January 2008
© SAP AG - University Alliances and The Rushmore Group, LLC All rights reserved.
© SAP AG and The Rushmore Group, LLC 2008

29. Customer Master Company Code – Acct Information
ECC 6.0
January 2008
Customer Master 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

30. 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

31. Customer Master Company Code – Correspondence
ECC 6.0
January 2008
Customer Master Company Code – Correspondence
Dunning Data
Dunning procedure
Dunning block
Dunning recipient
Correspondence
Accounting clerk
Acct at customer
Customer user
Payment Notices To
Customer – Sales
Accounting – Legal
Dunning data
Dunning procedure Key for dunning procedure used.
Dunning recipient Account number of recipient of dunning letters.
Dunning level System generated entry, which indicates dunning level reached by the last dunning run.
Last dunned Date of last dunning notice to this customer.
January 2008
© SAP AG - University Alliances and The Rushmore Group, LLC All rights reserved.
© SAP AG and The Rushmore Group, LLC 2008

32. Customer Master Company Code – Insurance
ECC 6.0
January 2008
Customer Master Company Code – Insurance
Export Credit Insurance
Policy Number
Institution Number
Amount Insure
Valid Until
Lead Months
Deductible
Correspondence
Account at customer Account number our company is listed under at the customer.
Account statement Indicator ID, which states when to create periodic account statements for this account
Customer user Name of accounting contact at customer.
Payment notices to
(Indicators) Customer (with or without cleared items), Sales, Accounting, Legal department.
January 2008
© SAP AG - University Alliances and The Rushmore Group, LLC All rights reserved.
© SAP AG and The Rushmore Group, LLC 2008

33. Customer Master Sales and Distribution – Sales
ECC 6.0
January 2008
Customer Master 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

34. 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

35. 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

36. 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

37. ECC 6.0
January 2008
Business Partners
Defines all of the parties involved in a business transaction
Differentiates between their roles
Customer
Carrier
Employees
Etc.
You enter data on business partners with whom your company has a business relationship in master records. Master records contain all data necessary for processing business transactions. This is known as master data.
If you enter all master data, you spend less time processing business transactions because the system proposes the master data in these transactions.
Financial Accounting and Logistics use master data. General data and data relevant to both departments is stored in shared master records to avoid duplication.
January 2008
© SAP AG - University Alliances and The Rushmore Group, LLC All rights reserved.
© SAP AG and The Rushmore Group, LLC 2008

38. ECC 6.0
Business Partners
January 2008
SAP automatically assigns a business partner to the customer master and to any transaction
There are four default business partner parties:
Payer (a legal entity)
Sold-to
Ship-to
Bill-to
They may be the same or different.
More business partner parties can be added to carry out additional business transactions
Facilitate the way our customers do business.
Business Partners 
Definition
Business partners are legal or natural persons with whom you have a business relationship.
Customers and vendors are business partners with whom you have a relationship involving the transfer of goods and services.
Use
Business partners have a number of different functions, described as partner functions, in connection with your company. You use partner functions to define the rights and responsibilities of each partner type in a business transaction. When you sell or order goods, for example, your business partners can assume partner functions such as:
Customer Partner Functions Vendor Partner Functions
Sold-to party Ordering address
Ship-to party Goods supplier
Bill-to party Invoice presented by
Payer Alternative payee
Different business partners may carry out one or more partner functions. For this reason, you can assign individual business partners a number of partner functions.
You manage data on business partners in master records. Data on partner functions is stored in these master records and used in Financial Accounting and Logistics.
Integration
A business partner can be a customer and a vendor at the same time if, for example, your customer also supplies goods to you or if a vendor is also one of your customers. In this case, you must create a customer master record and a vendor master record for the business partner. You can create a link between the two master records by entering the vendor number in the customer master record and the customer number in the vendor master record.
January 2008
© SAP AG - University Alliances and The Rushmore Group, LLC All rights reserved.
© SAP AG and The Rushmore Group, LLC 2008

39. Customer Account Group
ECC 6.0
January 2008
Customer Account Group
Customer masters are assigned to a customer account group
Through field status maintenance, account groups can be setup for one-time customers, regional customers, internal …
The customer account group controls both type and number range assignment for customers
Can be set up for type of vendors –
When you create a master record for a business partner, you must enter an account group. The account group determines:
Which screens and fields are necessary for entering master data
Whether you can or must make an entry in these fields
How master record numbers are assigned (externally by you or internally by the system) and the number range from which they are assigned
Which partner functions are valid
Whether the business partner is a one-time customer or one-time vendor
Additionally, for vendor master records only, the account group determines:
Whether default purchasing data in the vendor master is to be transferred to article master records and purchasing information records
Whether there are any other data retention levels below the purchasing organization level (for example, site or vendor sub-range level) at which data can be retained in the vendor master, and if so, what these are
January 2008
© SAP AG - University Alliances and The Rushmore Group, LLC All rights reserved.
© SAP AG and The Rushmore Group, LLC 2008

40. ECC 6.0
January 2008
Field Status
Field status controls the use of each field within the customer master determining whether a field is required, optional, suppressed or display only
Field status controls are also relevant to a specific activity — create, change, or display
The field status can be defined for many types of data. This controls if the field is required, optional, or display only. If you suppress a field, you also suppress its functionality.
January 2008
© SAP AG - University Alliances and The Rushmore Group, LLC All rights reserved.
© SAP AG and The Rushmore Group, LLC 2008

41. 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

42. 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

43. 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

44. 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

45. 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

46. 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

47. 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

48. Pricing A very robust module in SAP
ECC 6.0
Pricing
January 2008
A very robust module in SAP
Highly touted “World-class” functionality
Very easily tailored to meet business needs
Gross to net pricing for material
Can do just about anything
The pricing in SAP is world class. It functionality is both wide and deep enabling users to program varied pricing procedures to meet individual organizations needs.
The pricing is extendible: You can attach, or extend, external pricing programs or elements outside SAP for pricing
It also allows Gross to Net pricing: This allows discounts and reductions from the ‘master’ price.
January 2008
© SAP AG - University Alliances and The Rushmore Group, LLC All rights reserved.
© SAP AG and The Rushmore Group, LLC 2008

49. 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

50. 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

51. ECC 6.0
Pricing Components
January 2008
Pricing uses tables to match the condition of order to the applicable pricing routine
These routines can
Add/Subtract amounts, percentages
Give dollar, weight, quantity breaks/additions
Accrue
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 .
You can, for example, define whether a discount is calculated as a percentage or a fixed amount using the condition type.
These routines can adjust the price based upon the dollars, weight, quantity or any other field on the order, material master, customer master, or customer info record.
The system can also accrue amounts. This can be used for rebates, commissions or whatever a company determines necessary.
January 2008
© SAP AG - University Alliances and The Rushmore Group, LLC All rights reserved.
© SAP AG and The Rushmore Group, LLC 2008

52. ECC 6.0
Pricing Procedure
January 2008
Pricing uses one of possibly many procedures based upon
Item
Customer
Order type
Sales Area
The 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

53. Pricing Procedure – (continued)
ECC 6.0
Pricing Procedure – (continued)
January 2008
Pricing conditions for each item on the order
Pricing condition uses
Pricing procedure
Access sequence
Conditions type
Determines adjustments and price
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

54. Pricing Process Select a line Item in Sales Order PPEN000 Sales Area
ECC 6.0
Pricing Process
January 2008
Select a line Item in
Sales Order
PPEN000
Sales Area
S000-RE-01
Doc. Pric.
Proc.
OR=A
Cus. Pric.
43 = 1
Determine a
Pricing Procedure
Pricing Procedure = RVAJUS
Pricing Procedure
Contains List of
Condition Types
Condition Type PR00 = Price
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 = $9.50
January 2008
© SAP AG - University Alliances and The Rushmore Group, LLC All rights reserved.
© SAP AG and The Rushmore Group, LLC 2008

55. Pricing Process Line Item Pricing Proced. Det.
ECC 6.0
Pricing Process
January 2008
Line Item
Pricing Proced. Det.
CTyp points to Access Seq.
Access Seq. points to Cond. Tbls.
Cond. Tbls. contain the Item Pricing
PPEN000
Sales Area
Doc. PP
Cust. PP
PR00
Points to
PR02
Points to Cond. Tables
Cust. / Mat.
Price List / Cur / Mat. Material
N / A
$ 9.50
This slide is another example of the previous slide with a little more detail
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.
January 2008
© SAP AG - University Alliances and The Rushmore Group, LLC All rights reserved.
© SAP AG and The Rushmore Group, LLC 2008

56. Price Agreements Standard price agreements Product Customer
ECC 6.0
January 2008
Price Agreements
Standard price agreements
Product
Customer
Customer & material
Customer group & material group
Detailed price agreements
Pricing scales
Rebates
Customer expected price
You can group condition records together using agreements for the purpose of sales deals - comparable to rebate agreements.
You can define agreement types for promotions and sales deals and specify different condition types and condition tables.
Agreements can be determine adjustments in the pricing procedure:
These can be any combination of
Product
Customer
Customer/Material
Customer Type and material type
Scale Basis
In the standard system, a pricing scale can be based on any of the following criteria:
Value
Quantity
Gross weight
Net weight
Volume
A formula specific to your requirements
A rebate agreement usually consists of a number of individual agreements in the form of condition records. A rebate agreement and the condition records it contains are uniquely identified by a rebate agreement number.
The rebate agreement includes general information and terms that apply to all the condition records it contains. For example, the method of payment and the rebate recipient you specify for a rebate agreement will apply to all the condition records you create within the agreement.
Resolving disputed invoices costs some industries (for example, the consumer packaged goods industry) a great deal of time and money. Customers deduct disputed invoices from payments and staff members spend valuable time investigating and researching the reasons for the disputed payment. In addition, prolonged disputes can endanger supplier-customer relations. The extended pricing functions introduced in Release 2.2 enable you to take into account the customer's expected price. By entering the expected price during sales order processing and comparing it with your price, you can help avoid disputed invoices later.
January 2008
© SAP AG - University Alliances and The Rushmore Group, LLC All rights reserved.
© SAP AG and The Rushmore Group, LLC 2008

57. 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

58. Credit Limits and Checking – (continued)
ECC 6.0
January 2008
Credit Limits and Checking – (continued)
Credit representatives are able to check a customer’s credit situation to decide whether the customer should be granted credit
Works in distributed systems
Central financial accounting
Non-central sales and distribution on several sales and distribution computers
The following section describes the different ways in which you can access information in Credit Management. The table under "Activities" describes how to access these various functions.
Customer master record
The customer master record contains the data (address, telephone and fax number, dunning procedure, sales data and so on) that you require to be able to conduct business with the customer.
Account analysis
The account analysis function enables you to call up information on a customer account. You can then view the customer’s payment history (for example, do they usually qualify for cash discount? How many days early do they pay their items on average?). This information assists you in assessing a customer’s liquidity and likely payment record in the future.
Line items, line item longest overdue, most recent payment
Credit master sheet
The credit master sheet displays such credit data as the current and maximum credit limit, and the total of deliveries, orders, and invoices outstanding.
Credit overview
The credit overview shows certain additional data including dunning data, open items and texts on the customer.
Early warning list
This list displays which customers are to viewed as critical as determined by the credit check in the Sales and Distribution (SD) application component. A customer is classified as critical if, based on the data that you defined under Automatic Credit Control (in Customizing for Credit Management under Sales and Distribution ® Basic Functions ® Credit Management/Risk Management ® Credit Managment ), he or she would not satisfy the following checks (carried out using the information from the A/R summary), either now or in the near future:
a. Longest outstanding open item
b. Overdue open items
c. Highest dunning level permitted
d. Next date on which customer is checked
e. Age of the data in the A/R summary
f. Percentage of credit limit used up
Financial Information System (FIS)
You can use the FIS to carry out customer evaluations online, structured according to your own requirements. Due date analyses, payment history evaluations, and DSO figure calculations are just some of the functions you can perform.
You can summarize or breakdown the data produced in these reports - from open item display to the customer credit management data - to whatever degree you require. You can also edit and present the data from the reports graphically.
Sales Information System (SIS)
The SIS enables you to collect, summarize, and evaluate data from sales and distribution processing.
Central Financial Accounting and decentralized SD processing
The decentralized Sales and Distribution units all have independant credit management. This means maintenance of credit master data, checks in SD, and realeasing via the credit manager are all carried out decentrally.
As only credit-relevant data for the corresponding Sales and Distribution unit is available for credit checks on the decentralized Sales and Distribution units for the sales order, delivery and goods issue, and credit account data is also needed from the head office (for example, sum of open items, oldest open item, maximum dunning level), Financial Accounting (FI) makes the A/R Summary available.
With the help of the A/R Summary, the credit data can be collected in the central system, and sent, via ALE distribution functions, to decentralized Sales and Distribution processing, and can be evaluated. The A/R summary presents the inquiry in Financial Accounting for credit checks.
As the credit-relevant SD data (open sales order, delivery and billing document values) is not distributed, there are specific prerequisites for working with distributed systems.
January 2008
© SAP AG - University Alliances and The Rushmore Group, LLC All rights reserved.
© SAP AG and The Rushmore Group, LLC 2008

59. ECC 6.0
January 2008
Credit Check
You can use this function at any time within service processing to call up information about the current credit status of a customer
Credit limit can be checked manually or automatically
The system generally checks the planned costs without tax
If a customer has exceeded their credit limit, the system issues a warning
The credit information is real-time within the system.
To ensure quick and effective processing of credit holds, the SAP R/3 System offers your credit personnel a working environment that can be tailored to your own needs. A credit representative can generate an overview list of credit holds to be processed and, depending on his or her authorizations, process each document accordingly.
The overview list is the basis for the credit representative's work. The most important data is as follows:
Next shipping date
Credit account (customer number or name)
Document number
Credit value (document value)
Currency
Credit limit used (in percentage)
Terms of payment
Risk category
Total status of credit check
Credit status (blocking reasons)
Date on which the document was created
Credit representative who entered data
Document value class
Processing Blocked Sales and Distribution Documents
The credit representatives can sort the overview list according to various criteria and can specify exactly how the list is displayed. They can then review the credit situation of any customer and, according to credit policy, decide how to continue processing the sales and distribution documents.
The credit representative can do any of the following:
Grant the credit limit and release the document.
Do not grant the credit limit and cancel the document.
Forward the blocked document to another representative.
Recheck blocked documents.
Redetermine the priority criteria for blocked documents. This enables you to give priority to and release several documents with a low document value until their credit limit is completely used up, instead doing so for a single document with a high document value that has already exceeded its credit limit.
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.
You can define for each checking rule whether the system reacts with an error or a warning. In the case of a warning, the system automatically enters a credit status in the document and saves the document. The status text describes the result of the credit check. It tells you, for example, if the document was blocked because the customer's credit limit was exceeded. Depending on the requirements you define, the document is blocked for further processing for reasons of credit.
January 2008
© SAP AG - University Alliances and The Rushmore Group, LLC All rights reserved.
© SAP AG and The Rushmore Group, LLC 2008

60. Credit Check – (continued)
ECC 6.0
Credit Check – (continued)
January 2008
The checks can be carried out at various times during the sales order cycle, from order receipt to delivery
You can define a credit check for any valid combination of the following data:
Risk category
Document credit group
Credit control area
The checks can be carried out at various times during the sales order cycle, from order receipt to delivery.
According to your credit policy, you define risk categories and assign them to individual customers, along with specific credit limits. In addition, you define credit groups for document types, known as document credit groups. Document credit groups combine order types and delivery types for credit control purposes. You can define a credit check for any valid combination of the following data:
Credit control area
Risk category
Document credit group
January 2008
© SAP AG - University Alliances and The Rushmore Group, LLC All rights reserved.
© SAP AG and The Rushmore Group, LLC 2008

61. 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

62. 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

63. 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

64. Assignment of Sales Area to Pricing Procedure
ECC 6.0
January 2008
Assignment of Sales Area to Pricing Procedure
Assignment of Pricing Procedure uses the combination of:
Sales Area
Document Pricing Procedure
Customer Pricing Procedure
Each combination of these has a pricing procedure assigned
The condition types used to post difference values in credit/debit self-billing documents are, like all condition types, linked with revenue account determination in Financial Accounting. Therefore, they are important for determining the account to which values are posted.
Revenue recognition uses revenue account determination. To set up revenue account determination, use transaction VKOA.
For example, you can allocate a freight condition to a freight revenue account, or a surcharge for packaging costs to a corresponding account for packaging revenues.
January 2008
© SAP AG - University Alliances and The Rushmore Group, LLC All rights reserved.
© SAP AG and The Rushmore Group, LLC 2008

65. ECC 6.0
Availability Check
January 2008
For determining the material availability date, SAP can include specific stocks below, if selected:
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

66. Credit Checking Static Credit Limit Check
ECC 6.0
Credit Checking
January 2008
Static Credit Limit Check
Open Orders
Open Deliveries
Open Billing documents
Open Items (accounts receivable)
Dynamic credit limit with credit horizon check (future dates)
Credit check to maximum document value (per order)
Static Credit Limit Check
The customer's credit exposure may not exceed the established credit limit. The credit exposure is the total combined value of the following documents:
- Open orders
- Open deliveries
- Open billing documents
- Open items (accounts receivable)
The open order value is the value of the order items which have not yet been delivered. The open delivery value is the value of the delivery items which have not yet been invoiced. The open invoice value is the value of the billing document items which have not yet been forwarded to accounting. The open items represent documents that have been forwarded to accounting but not yet settled by the customer.
Dynamic Credit Limit Check with Credit Horizon
The customer's credit exposure is split into a static part; open items, open billing, and delivery values (see above), and a dynamic part, the open order value. The open order value includes all undelivered or only partially delivered orders. The value is calculated on the shipping date and stored in an information structure according to a time period that you specify (days, weeks, or months). When you define the credit check, you can then specify a particular horizon date in the future (for example: 10 days or 2 months, depending on the periods you specify). For the purposes of evaluating credit, you want the system to ignore all open orders that are due for delivery after the horizon date. The sum of the static and dynamic parts of the check may not exceed the credit limit.
Maximum Document Value
The sales order or delivery value may not exceed a specific value which is defined in the credit check. The value is stored in the currency of the credit control area. This check is useful if the credit limit has not yet been defined for a new customer. It is initiated by a risk category which is defined specifically for new customers.
January 2008
© SAP AG - University Alliances and The Rushmore Group, LLC All rights reserved.
© SAP AG and The Rushmore Group, LLC 2008

67. 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

68. 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

69. Sales & Distribution
Master Data
PEN, Inc. EGN Enterprise Systems Configuration (Professional MSEM) Fall, 2012

70. Enterprise Structure in Pen Inc.
Plant
(P _ _ _)
Client (600)
Chart of
Accounts (C _ _ _)
Company
Code (C _ _ _)
Fiscal Year
Variant (2012)
Credit Control
Area (C _ _ _)
Shipping
Point (S _ _ _)
Sales
Org. S _ _ _
Distribution
Channel (RE, WH)
Division (01)
Sales Area (S _ _ _)
Controlling Area (C _ _ _)
SL10
SL20

71. Customer Master Address Data:

72. Customer Master Sales Areas Data:

73. Customer Master Price Data:

74. Customer Master Credit Data:

75. 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
S_ _ _ RE 01 A 1
RVAAPC WH

76. Exercises: 128. Create Sales Revenue Account
129. Create Sales Revenue Deductions Account
131. Create Customer
132. Create Ship-to-Party
133. Assign Ship-to Party to Customer
134. Create Material Prices
135. Create Customer Specific Material Price
136. Create Customer Discount
137. Establish Credit Limit for Customers
138. Assign Sales Areas to Pricing Procedure
141. Create Shipping Point Determination
142. Create Account Assignment Key
143. Check Stock Status
211A: Maintain Cost Center Standard Hierarchy