28
© SAP AG Phase III: Fulfillment SAP University Alliances Version 2.2 Authors Simha R. Magal Stefan Weidner Tom Wilder Product SAP ERP 6.0 EhP4 Global Bike Inc. Level Beginner Focus Configuration: The Fulfillment Process

© SAP AG Phase III: Fulfillment SAP University Alliances Version 2.2 Authors Simha R. Magal Stefan Weidner Tom Wilder Product SAP ERP 6.0 EhP4 Global Bike

Embed Size (px)

Citation preview

Page 1: © SAP AG Phase III: Fulfillment SAP University Alliances Version 2.2 Authors Simha R. Magal Stefan Weidner Tom Wilder Product SAP ERP 6.0 EhP4 Global Bike

© SAP AG

Phase III: Fulfillment

SAP University Alliances

Version 2.2

Authors Simha R. MagalStefan WeidnerTom Wilder

ProductSAP ERP 6.0 EhP4Global Bike Inc.

LevelBeginner

FocusConfiguration: The Fulfillment Process

Page 2: © SAP AG Phase III: Fulfillment SAP University Alliances Version 2.2 Authors Simha R. Magal Stefan Weidner Tom Wilder Product SAP ERP 6.0 EhP4 Global Bike

Configuration

Page 2© SAP AG

Agenda

Enterprise structure

Business rules and parameters

Master data

Process execution (testing)

Exercises

Page 3: © SAP AG Phase III: Fulfillment SAP University Alliances Version 2.2 Authors Simha R. Magal Stefan Weidner Tom Wilder Product SAP ERP 6.0 EhP4 Global Bike

Configuration

Page 3© SAP AG

Enterprise structure

Enterprise structure elements- Client- Company code- Plant (shipping plant)- Storage location- Sales organization- Distribution channel- Division- Sales area- Shipping point

Define / maintain

Assign

Page 4: © SAP AG Phase III: Fulfillment SAP University Alliances Version 2.2 Authors Simha R. Magal Stefan Weidner Tom Wilder Product SAP ERP 6.0 EhP4 Global Bike

Configuration

Page 4© SAP AG

Sales Organization

Used to divide the market based on geographic regions

Responsible for- Distributing goods and services- Negotiating sales conditions

Highest level of aggregation in sales-related reporting

A company code must have at least one sales organization

Page 5: © SAP AG Phase III: Fulfillment SAP University Alliances Version 2.2 Authors Simha R. Magal Stefan Weidner Tom Wilder Product SAP ERP 6.0 EhP4 Global Bike

Configuration

Page 5© SAP AG

Sales Organization

Page 6: © SAP AG Phase III: Fulfillment SAP University Alliances Version 2.2 Authors Simha R. Magal Stefan Weidner Tom Wilder Product SAP ERP 6.0 EhP4 Global Bike

Configuration

Page 6© SAP AG

Distribution Channel

Responsible for getting materials to customers

Used to - Differentiate distribution strategies or approaches- Different pricing, responsibilities

• Wholesale sales, retail sales, Internet sales- Statistics and reporting at the DC level

A sales organization must have at least one distribution channel

Page 7: © SAP AG Phase III: Fulfillment SAP University Alliances Version 2.2 Authors Simha R. Magal Stefan Weidner Tom Wilder Product SAP ERP 6.0 EhP4 Global Bike

Configuration

Page 7© SAP AG

Distribution Channel

Page 8: © SAP AG Phase III: Fulfillment SAP University Alliances Version 2.2 Authors Simha R. Magal Stefan Weidner Tom Wilder Product SAP ERP 6.0 EhP4 Global Bike

Configuration

Page 8© SAP AG

Division

Used to consolidate materials with similar characteristics- Different sales strategies, pricing agreements- Statistics and reporting at the DC level- Associated with product lines

A sales organization must have at least one division

Can be assigned to multiple sales organizations

Division is cross company code data

Page 9: © SAP AG Phase III: Fulfillment SAP University Alliances Version 2.2 Authors Simha R. Magal Stefan Weidner Tom Wilder Product SAP ERP 6.0 EhP4 Global Bike

Configuration

Page 9© SAP AG

Enterprise structure: Division

Page 10: © SAP AG Phase III: Fulfillment SAP University Alliances Version 2.2 Authors Simha R. Magal Stefan Weidner Tom Wilder Product SAP ERP 6.0 EhP4 Global Bike

Configuration

Page 10© SAP AG

Sales Area

Made up of three other organizational elements- Sales organization- Distribution channel- Division

Page 11: © SAP AG Phase III: Fulfillment SAP University Alliances Version 2.2 Authors Simha R. Magal Stefan Weidner Tom Wilder Product SAP ERP 6.0 EhP4 Global Bike

Configuration

Page 11© SAP AG

Sales Area

Page 12: © SAP AG Phase III: Fulfillment SAP University Alliances Version 2.2 Authors Simha R. Magal Stefan Weidner Tom Wilder Product SAP ERP 6.0 EhP4 Global Bike

Configuration

Page 12© SAP AG

Shipping Point

A physical location from which outbound deliveries are sent- Loading dock- Mail room- Rail depot- Group of employees (to handle expedited orders)

A plant must have at least one shipping point

A shipping point can be assigned to many plants

Page 13: © SAP AG Phase III: Fulfillment SAP University Alliances Version 2.2 Authors Simha R. Magal Stefan Weidner Tom Wilder Product SAP ERP 6.0 EhP4 Global Bike

Configuration

Page 13© SAP AG

Shipping Point

Page 14: © SAP AG Phase III: Fulfillment SAP University Alliances Version 2.2 Authors Simha R. Magal Stefan Weidner Tom Wilder Product SAP ERP 6.0 EhP4 Global Bike

Configuration

Page 14© SAP AG

Agenda

Enterprise structure

Business rules and parameters

Master data

Process execution (testing)

Exercises

Page 15: © SAP AG Phase III: Fulfillment SAP University Alliances Version 2.2 Authors Simha R. Magal Stefan Weidner Tom Wilder Product SAP ERP 6.0 EhP4 Global Bike

Configuration

Page 15© SAP AG

Business Rules and Parameters

Shipping point determination

Automatic account determination- Cost of goods sold expense account- Revenue accounts

Pricing procedures- Define pricing procedures for sales areas

Rules for determining business area- Define for sales area

Page 16: © SAP AG Phase III: Fulfillment SAP University Alliances Version 2.2 Authors Simha R. Magal Stefan Weidner Tom Wilder Product SAP ERP 6.0 EhP4 Global Bike

Configuration

Page 16© SAP AG

Agenda

Enterprise structure

Business rules and parameters

Master data

Process execution (testing)

Exercises

Page 17: © SAP AG Phase III: Fulfillment SAP University Alliances Version 2.2 Authors Simha R. Magal Stefan Weidner Tom Wilder Product SAP ERP 6.0 EhP4 Global Bike

Configuration

Page 17© SAP AG

Master Data

Material master

Customer master

Pricing Conditions

Customer-material info record

Output Conditions

Page 18: © SAP AG Phase III: Fulfillment SAP University Alliances Version 2.2 Authors Simha R. Magal Stefan Weidner Tom Wilder Product SAP ERP 6.0 EhP4 Global Bike

Configuration

Page 18© SAP AG

Master Data: Material Master

Basic Data

Sales: Sales Organization- Includes data specific to a combination of sales organization and

distribution channels- Examples include: delivering plant, sales units (unit of measure),

minimum quantities (order, delivery)

Sales: General/Plant- Includes data specific to a plant- Examples include: handling requirements (refrigeration), loading (hand

cart, forklift)

Demo• Review material master• Review fulfillment related tabs

Page 19: © SAP AG Phase III: Fulfillment SAP University Alliances Version 2.2 Authors Simha R. Magal Stefan Weidner Tom Wilder Product SAP ERP 6.0 EhP4 Global Bike

Configuration

Page 19© SAP AG

Master Data: Customer

General Data (Client)- Number, name

Financial/ Accounting data (Company code)- Reconciliation account

Sales Area data (Sales area)- Terms

Demo• Review customer master• Review data in 3 segments

Page 20: © SAP AG Phase III: Fulfillment SAP University Alliances Version 2.2 Authors Simha R. Magal Stefan Weidner Tom Wilder Product SAP ERP 6.0 EhP4 Global Bike

Configuration

Page 20© SAP AG

Multiple Definitions of a Customer

Page 21: © SAP AG Phase III: Fulfillment SAP University Alliances Version 2.2 Authors Simha R. Magal Stefan Weidner Tom Wilder Product SAP ERP 6.0 EhP4 Global Bike

Configuration

Page 21© SAP AG

Customer - Material Info Record

Intersection data for one customer and one material- Data specific to the combination of customer and material

Supersedes data in customer master and material master

Examples of data- Cross references customer material numbers, descriptions- Specific terms specific to material/customers

• Alternate delivery plant, shipping terms/methods, tolerances, partial deliveries (e.g. not accepted for this material)

Page 22: © SAP AG Phase III: Fulfillment SAP University Alliances Version 2.2 Authors Simha R. Magal Stefan Weidner Tom Wilder Product SAP ERP 6.0 EhP4 Global Bike

Configuration

Page 22© SAP AG

Master Data: Pricing Conditions

Prices- Material price- Customer specific price

Freight- InCoTerms

Surcharges and discounts- For customer, material, or combination

Taxes

Demo• Review customer prices

Page 23: © SAP AG Phase III: Fulfillment SAP University Alliances Version 2.2 Authors Simha R. Magal Stefan Weidner Tom Wilder Product SAP ERP 6.0 EhP4 Global Bike

Configuration

Page 23© SAP AG

Master Data: Output Conditions

Sent to customers using a variety of media

Examples of output- Quotation, order confirmation, invoices

Media- Mail, fax, EDI

Master data includes- Output type- Output medium- Time (immediate or later)- Partner function

Page 24: © SAP AG Phase III: Fulfillment SAP University Alliances Version 2.2 Authors Simha R. Magal Stefan Weidner Tom Wilder Product SAP ERP 6.0 EhP4 Global Bike

Configuration

Page 24© SAP AG

Agenda

Enterprise structure

Business rules and parameters

Master data

Process execution (testing)

Exercises

Page 25: © SAP AG Phase III: Fulfillment SAP University Alliances Version 2.2 Authors Simha R. Magal Stefan Weidner Tom Wilder Product SAP ERP 6.0 EhP4 Global Bike

Configuration

Page 25© SAP AG

Process execution

Page 26: © SAP AG Phase III: Fulfillment SAP University Alliances Version 2.2 Authors Simha R. Magal Stefan Weidner Tom Wilder Product SAP ERP 6.0 EhP4 Global Bike

Configuration

Page 26© SAP AG

Agenda

Enterprise structure

Business rules and parameters

Master data

Process execution (testing)

Exercises

Page 27: © SAP AG Phase III: Fulfillment SAP University Alliances Version 2.2 Authors Simha R. Magal Stefan Weidner Tom Wilder Product SAP ERP 6.0 EhP4 Global Bike

Configuration

Page 27© SAP AG

Exercises

3.1 - Enterprise Structure- Configure the enterprise structure

3.2 - Business Rules- Define business rules

3.3 - Master Data- Material, Customer (copy from 00 where possible)

3.4 - Testing- Execute simple fulfillment process

Appendices- Exercises provide detailed instructions for one or few objects (e.g,

once cost center, once vendor, etc.)- Appendices provide data from additional objects (cost centers, etc.)- Don’t forget them!!!!

Page 28: © SAP AG Phase III: Fulfillment SAP University Alliances Version 2.2 Authors Simha R. Magal Stefan Weidner Tom Wilder Product SAP ERP 6.0 EhP4 Global Bike

Configuration

Page 28© SAP AG

Agenda

Enterprise structure

Business rules and parameters

Master data

Process execution (testing)

Exercises