24
SAP SD Overview Training Enterprise Structure

SD Overview Enterprise Structure

Embed Size (px)

Citation preview

Page 1: SD Overview Enterprise Structure

SAP SD Overview Training Enterprise Structure

Page 2: SD Overview Enterprise Structure

Nexus System ResourcesLocal needs, Global solution

• System Applications and Products in Data

Processing

• Integrated Software

• ERP Software

SAP ?

Page 3: SD Overview Enterprise Structure

Nexus System ResourcesLocal needs, Global solution

R/3Client / Server

ABAP/4

FIFinancial

Accounting

COControlling

AMFixed Assets

Mgmt.

TRTreasury

WFWorkflow

ISIndustry

Solutions

MMMaterials

Mgmt.

HRHuman

Resources

SDSales &

Distribution

PPProductionPlanning

QMQualityMgmt.

PMPlant

Maintenance

Logistics

HumanResources

Financials

SAP MODULES

Page 4: SD Overview Enterprise Structure

Nexus System ResourcesLocal needs, Global solution

Objectives

After this presentation, you should Have a clear picture about the operation in SAP R/3 system, Have more understanding about the process in SAP R/3, Have a general idea how to design SAP R/3 for your organization

Page 5: SD Overview Enterprise Structure

Nexus System ResourcesLocal needs, Global solution

Documents in the Sales and Distribution Processing System

MATERIALS

MGMT

SalesInformation

System

USD

Sales support

Sales

Shipping

Billing

Financial accounting

Delivery

Debit memo Credit memoInvoice

Delivery freeof charge

Subsequentdelivery free

of charge ReturnsOrder(Rush/Cash)

Contract

Schedulingagreement

Contact

Inquiry

Quotation

Transport

PRODUCTION

PLANNING

Goods Issue

Presenter
Presentation Notes
This slide represents the relationship between the processes in sales order processing in the SAP System. The sequence from top to bottom represents the order of events in the sales process. The boxes represent sales and financial accounting documents. Sales activities and promotions are documents for sales support in pre-sales. Sales documents are documents that are entered during pre-sales and sales order processing. Inquiries, quotations, contracts, scheduling agreements and standard orders are examples of sales document types. Outbound deliveries, transfer orders and shipments are documents in shipping processing. The goods issue document contains changes involving stock and is the basis for the relevant accounting documents. The billing document is a document in billing and is the basis for the relevant accounting documents. The left and right sections of this slide represent key interfaces between Sales and Distribution and the Sales Information System (SAP data warehouse), Articles Management and Production Planning.
Page 6: SD Overview Enterprise Structure

Nexus System ResourcesLocal needs, Global solution

Enterprise Structures in Sales and Distribution

Master Data in Sales and Distribution

Overview of Sales Processes

Complains Processes

Special Functions for Sales Processes

Report and Sales Information System

Course Contents

Page 7: SD Overview Enterprise Structure

Nexus System ResourcesLocal needs, Global solution

Enterprise Structures in

Sales and Distribution

Page 8: SD Overview Enterprise Structure

Nexus System ResourcesLocal needs, Global solution

Enterprise Structures in Sales and Distribution

Master Data in Sales and Distribution

Overview of Sales Processes

Complains Processes

Special Functions for Sales Processes

Report and Sales Information System

Preface

Course Contents

Page 9: SD Overview Enterprise Structure

Nexus System ResourcesLocal needs, Global solution

Unit Objectives

Identify organizational units in the SAP Systemthat are relevant for Sales and Distribution

Describe the essential characteristics of theseorganizational units

Form organizational structures using theorganizational units

Form organizational structures usingcombinations of organizational units

At the conclusion of this unit, you will be able to:

Page 10: SD Overview Enterprise Structure

Nexus System ResourcesLocal needs, Global solution

Overview Diagram : Enterprise Structures

Shipping

Enterprise StructuresSales & Distribution

Pre-Sales Activities

Sales OrderProcessing

Inventorysourcing

Payment

Billing

Invoice

Page 11: SD Overview Enterprise Structure

Nexus System ResourcesLocal needs, Global solution

Enterprise Structure

Group

Company

Factory

Wholesale

Product line

RR//33ll Company codeCompany code

Sales organizationSales organizationll

ll DistributionDistribution channelchannel

DivisionDivisionl

ll Storage locationStorage location

ll SitePlant

ll ClientClient

Storage location

Product line

Retail

Sales department

Affiliate

Page 12: SD Overview Enterprise Structure

Nexus System ResourcesLocal needs, Global solution

Document

Organizational Units in Sales and Distribution

RR//33ll Company codeCompany code

ll Sales AreaSales Area

Sales organizationSales organization

DistributionDistribution channelchannel

DivisionDivision

ll SitePlant

ll Storage locationStorage location

ll shipping pointShipping point

Presenter
Presentation Notes
Organizational units in the R/3 System represent the structure of an enterprise organization. Organizational units represent the legal and organizational views of an enterprise. The Sales and Distribution module uses some organizational units that can only represent sales and distribution processes, such as sales organization, distribution channel, division or shipping point. Other organizational units, such as company code or Site, are used in Sales and Distribution and in other modules in the R/3 System. You can represent your enterprise structure using organizational units based on your business processes. This is not a complete list of all organizational units relevant for the sales and distribution processes in the R/3 System.
Page 13: SD Overview Enterprise Structure

Nexus System ResourcesLocal needs, Global solution

Organizational Units : Sales Organization

Responsible for:

l distributing goods and services

l negotiating sales conditions

l product liability and rights of recourse

Sales organization

Presenter
Presentation Notes
The sales organization is an organizational unit in Logistics which groups the enterprise according to the requirements of sales and distribution. A sales organization is responsible for distributing goods and services. Therefore, it is also liable for the sold products and responsible for the customers' rights of recourse. The sales organization is also used to take, for example, a regional, national or international subdivision of the market into account. A sales organization is uniquely assigned to a company code. More than one sales organization can be assigned to a company code. If you use the Sales and Distribution module, you need at least one sales organization. You maintain own master data for a sales organization. In the sales statistics, the sales organization is the highest summation level. All items in a sales and distribution document, that is, all items of an order, an outbound delivery or a billing document, belong to a sales organization.
Page 14: SD Overview Enterprise Structure

Nexus System ResourcesLocal needs, Global solution

ClientCompany code 2000

1020

Salesorganization

1000

Salesorganization

Sales organization

2000

Company code 1000

Organizational Units : Sales Organization - Con’t

Page 15: SD Overview Enterprise Structure

Nexus System ResourcesLocal needs, Global solution

Organizational Units : Sales Organization - Con’t

Client

1000

Salesorganization

Company code 1000

Page 16: SD Overview Enterprise Structure

Nexus System ResourcesLocal needs, Global solution

Organizational Units : Distribution Channel

l is a means through which sales materials reach the customer

l represents your strategies to distribute goods and/or servicesto your customer

l for example : whole sale trade, retail trade, internet trade, ...

Sales organization

Distribution Channel 1 Distribution Channel 2

Presenter
Presentation Notes
A distribution channel is a means through which salable Articles or services reach the customer. Several distribution channels can be assigned to a sales organization. If you use the Sales and Distribution module, you need at least one distribution channel. For example, it is used to: Define responsibilities, Achieve flexible pricing and Differentiate sales statistics
Page 17: SD Overview Enterprise Structure

Nexus System ResourcesLocal needs, Global solution

l Represents a product linel for example : motorcycles, spare parts, service, ...

Sales organization

Division 1 Division 2

Organization Units : Division

Presenter
Presentation Notes
A division is used to group Articles and services. A sales organization can have several divisions assigned to it, for which it is responsible. If you use the Sales and Distribution module, you will need at least one division. The system uses the division to determine the sales areas a Article or a service is assigned to. A division can, for example, represent a product group. Therefore, you can, for example, restrict price agreements with a customer to a certain division. You can also conduct statistical analysis by division.
Page 18: SD Overview Enterprise Structure

Nexus System ResourcesLocal needs, Global solution

Salesorganization

Distributionchannel

Division

2 Retail trade

2 Motorcycles 3 Computers 3 Computers

5 Internet

2 Cologne

1 Pumps

1 Wholesale trade

2 Motorcycles

122

123

153

212

2

1 Munich

11

Salesareas

Sales Area

Presenter
Presentation Notes
A sales area is a combination of the sales organization, distribution channel, and division. It defines the distribution channel a sales organization uses to sell products from a certain division. Each sales and distribution document is assigned to exactly one sales area. This assignment cannot be changed. A sales area can belong to only one company code. This relationship is created by assigning the sales organization. During the processing of sales and distribution documents, the system accesses various master data, according to the sales area. This master data includes, for example, customer master data, Article master data, prices, and discounts. In addition, the system carries out several checks concerning the validity of certain entries according to the sales area. Note: A simple organizational structure can be better than a complex one. For example, it simplifies updating master data. Do not define complex organizational structures in order to have detailed reporting options. Use fields on the master data screen.
Page 19: SD Overview Enterprise Structure

Nexus System ResourcesLocal needs, Global solution

Sales Office and Sales Group (Optional)

Sales office

Sales group

Sales rep.

KK1 KK2

Joseph

Sales Area

John Scott Michael Jane Diana Grace

003 004 005001 002

Page 20: SD Overview Enterprise Structure

Nexus System ResourcesLocal needs, Global solution

Sales Organizations and Plants

Company code 2000Company code 1000

Client

Plant 4 Plant 5

Sales organization

2000

Plant 1 Plant 3Plant 2

Salesorganization

1100

Salesorganization

1000

Page 21: SD Overview Enterprise Structure

Nexus System ResourcesLocal needs, Global solution

Plant and Storage Location

(Delivering ) plant

Storage location

ABBC

B

11

Plant 1 Plant 2

21

22

Plant 3

Page 22: SD Overview Enterprise Structure

Nexus System ResourcesLocal needs, Global solution

Shipping points and Plants

Shipping points

Client

Plants Plant3Plant2Plant1

Shipping Point1 Shipping Point2

Loading points Ramp A Ramp B Ramp C

Presenter
Presentation Notes
Shipping is an integrated module of sales and distribution processing. The shipping point is the highest-level organizational unit of shipping that controls your shipping activities. Each outbound delivery is processed by one shipping point. The shipping point can be a loading ramp, a mail depot, or a rail depot. It can also be, for example, a group of employees responsible (only) for organizing urgent deliveries. You assign a shipping point in the SAP System at Site level. A shipping point is a physical place and should be near the delivering Site. More than one shipping point can be assigned to a Site. You can also assign several Sites to a shipping point. This can also be appropriate for Sites in physical proximity.
Page 23: SD Overview Enterprise Structure

Nexus System ResourcesLocal needs, Global solution

Shipping points and Plants – Con’t

Plant 1

A

B

Plant 2

Shippingpoint 2

Shippingpoint 1

Shippingpoint 4

Shippingpoint 3

Page 24: SD Overview Enterprise Structure

Nexus System ResourcesLocal needs, Global solution

THANK YOU