IAU210 - Automotive Supplier PDF

IAU210 SAP: Automotive: Supplier
IAU210
Release 1.0 16.01.2004

IAU210 SAP: Automotive: Supplier.............................................................................................................................0-1
Copyright ..................................................................................................................................................................0-2
Target Audience....................................................................................................................................................0-4
R/3 Integration Model ...........................................................................................................................................0-5
Curriculum Path Automotive 1 ...............................................................................................0-6
Curriculum Path Automotive 2 ...............................................................................................0-7
Course Contents ....................................................................................................................................................0-8
Contents ................................................................................................................................................................0-9
IAU210 Introduction: Contents.................................................................................................................................1-1
IAU210 Introduction: Course Goals .....................................................................................................................1-2
IAU210 Introduction: Course Objectives..............................................................................................................1-3
IAU210 Introduction: Business Scenario 1..........................................................................................................1-4
IAU210 Introduction: Business Scenario 2...........................................................................................................1-5
The Automotive Logistics Chain: Objectives .......................................................................................................1-6
Complete Logistics System for Networked Value-Added Chains ........................................................................1-7
Automotive Logistics Chain: Levels 1....................................................................................................1-8
Automotive Logistics Chain: Levels 2..................................................................................................................1-9
Business Process Without External ServiceAgent 1 ........................................................................................1-10
Business Process Without External ServiceAgent2 ............................................................................................1-11
Notes on System Example ..................................................................................................................................1-16
Business Process With External Service Agent ..................................................................................................1-17
Process Overview for Supplier............................................................................................................................1-18
The Automotive Logistics Chain: Summary.......................................................................................................1-19
Overview of EDI Procedure: Objectives.............................................................................................................1-20
Terminology........................................................................................................................................................1-21
R/3 EDI Procedure - Starting Point.....................................................................................................................1-22
R/3 EDI - SD Procedure......................................................................................................................................1-23
R/3 EDI - MM Procedure....................................................................................................................................1-24
R/3 EDI Procedure ..............................................................................................................................................1-25
EDI Scenario for Supplier (Extract) 1.................................................................................................1-26
EDI Scenario for Supplier 2 ................................................................................................1-27
Overview of EDI Standards ................................................................................................................................1-28
EDI Procedure: Summary ...................................................................................................................................1-29
IAU210 Introduction: Summary .........................................................................................................................1-30
SD Scheduling Agreement Processing: Contents......................................................................................................2-1
SD Scheduling Agreement Processing: Unit Objectives.......................................................................................2-2
SD Scheduling Agreement Processing: Business Scenario...................................................................................2-3
SD Scheduling Agreements: Objectives ...............................................................................................................2-4
Business Process (Section)....................................................................................................................................2-5
- .............................................................................................................................................................................2-6
- .............................................................................................................................................................................2-7
SD Scheduling Agreement - Initial Screen ...........................................................................................................2-8
- .............................................................................................................................................................................2-9
Types of Delivery Schedule ................................................................................................................................2-10
Relevance of Schedules for Delivery and MRP ..................................................................................................2-11
Creating Forecast and JIT Delivery Schedules ...................................................................................................2-12
- ...........................................................................................................................................................................2-13
Monitoring Changes............................................................................................................................................2-15
Cumulative Quantities - Definition .....................................................................................................................2-16
Cumulative Quantities - Examples......................................................................................................................2-17
Cumulative Quantities - Quantity Adjustment ....................................................................................................2-18
Supplier Go-Aheads ............................................................................................................................................2-19
Correction Delivery Note....................................................................................................................................2-20
Automatic Fiscal Year Change1 .........................................................................................................................2-21
Packing Proposal.................................................................................................................................................2-25
- ...........................................................................................................................................................................2-26
Automatic Determination of Scheduling Agreement for Delivery ScheduleStep 1 ............................................2-27
Automatic Determination of Scheduling Agreement for Delivery Schedule Step 2 ...........................................2-28
Automatic Determination of Scheduling Agreement for Delivery Schedule Step 3 ...........................................2-29
Error Processing..................................................................................................................................................2-30
SD Scheduling Agreement Processing : Summary .............................................................................................2-31
Delivery Orders: Objectives................................................................................................................................2-32
Delivery Order Procedure ...................................................................................................................................2-33
Delivery Order Procedure 1 ................................................................................................................................2-34
Delivery Order Procedure2 .................................................................................................................................2-35
Pick-Up Sheet .....................................................................................................................................................2-36
- ...........................................................................................................................................................................2-37
Scheduling Agreements for Delivery Orders ......................................................................................................2-38
Delivery Orders - Structure .................................................................................................................................2-39
- ...........................................................................................................................................................................2-40
- ...........................................................................................................................................................................2-41
Delivery Orders: Summary .................................................................................................................................2-42
Shipping Activities: Contents ...................................................................................................................................3-1
Shipping Activities: Unit Objectives.....................................................................................................................3-2
Shipping Activities: Business Scenario.................................................................................................................3-3
Shipping Activities: Business Process (Section)...................................................................................................3-4
Shipping Overview Diagram.................................................................................................................................3-5
Messages in Shipping............................................................................................................................................3-6
- .............................................................................................................................................................................3-8
Shipping Point Determination...............................................................................................................................3-9
Route Determination in Sales Documents ..........................................................................................................3-10
- ...........................................................................................................................................................................3-11
Delivery Structure ...............................................................................................................................................3-12
- ...........................................................................................................................................................................3-13
- ...........................................................................................................................................................................3-14
Picking with WM/Lean WM: Process ................................................................................................................3-15
Confirming Transfer Orders................................................................................................................................3-16
Shipping Overview Diagram...............................................................................................................................3-17
General Requirements for Packing .....................................................................................................................3-18
Shipping Materials and Shipping Units ..............................................................................................................3-19
Packing Shipping Units.......................................................................................................................................3-20
Packing in Orders, Deliveries, and Shipments ....................................................................................................3-21
Managing Stock for Shipping Materials .............................................................................................................3-22
Supplier-Owned Packaging Material ..................................................................................................................3-23
Customer-Owned Packaging Material ................................................................................................................3-24
Disposable Packaging Material...........................................................................................................................3-25
Receiving Returnable Packaging Materials:Which Transaction? .......................................................................3-26
- ...........................................................................................................................................................................3-27
Delivery Restriction - Shipment..........................................................................................................................3-28
Shipment Documents and their Functions...........................................................................................................3-29
Packing and Loading for Shipment.....................................................................................................................3-30
Shipping Overview Diagram...............................................................................................................................3-31
Goods Issue .........................................................................................................................................................3-32
Effects of Goods Issue ........................................................................................................................................3-33
- ...........................................................................................................................................................................3-34
Delivery Communication Requirements .............................................................................................................3-35
Shipping Activities: Summary ............................................................................................................................3-36
Billing, Credit Memo Procedure: Contents...............................................................................................................4-1
Billing, Credit Memo Procedure: Unit Objectives ................................................................................................4-2
Billing, Credit Memo Procedure: Business Scenario ............................................................................................4-3
Billing: Objectives ................................................................................................................................................4-4
Business Process (Section)....................................................................................................................................4-5
Structure of the Billing Document ........................................................................................................................4-6
Effects of Billing Document Creation...................................................................................................................4-7
Options for Creating Invoices ...............................................................................................................................4-8
Billing: Summary..................................................................................................................................................4-9
Evaluated Receipt Settlement, Credit Memo Procedure, Payment: Objectives ..................................................4-10
Goods Receipt .....................................................................................................................................................4-11
Information Contained in a Shipping Notification..............................................................................................4-12
Automatic Goods Receipt Settlement .................................................................................................................4-13
Automatic Payment Program ..............................................................................................................................4-14
- ...........................................................................................................................................................................4-15
Scheduling Agreement Processing With an External Service Agent: Unit Objectives .............................................5-1
Scheduling Agreement Processing With an External Service Agent: Business Scenario .....................................5-2
Automotive Logistics Chain: Levels 2..................................................................................................................5-3
Business Process with External Service Agent 1 ..................................................................................................5-4
EDI Data Flow: Shipping Via External Service Agents .....................................................................................5-10
Scheduling Agreement Elements ........................................................................................................................5-11
Scheduling Agreement Elements (2)...................................................................................................................5-12
Delivery to the External Service Agent (Consignment Fill-Up) .........................................................................5-13
Notes on Packaging Materials.............................................................................................................................5-14
Delivery from External Service Agent to Customer ...........................................................................................5-15
Scheduling Agreement Processing with an External Service Agent: Summary .................................................5-16
Production Processing: Contents...............................................................................................................................6-1
Production Processing: Unit Objectives................................................................................................................6-2
Production Processing: Business Scenario............................................................................................................6-3
Planning Delivery Schedules - Internal Delivery Schedules: Objectives..............................................................6-4
- .............................................................................................................................................................................6-5
Functions of the Planning Delivery Schedule .......................................................................................................6-6
Planning Delivery Schedule - Overview ...............................................................................................................6-7
- .............................................................................................................................................................................6-8
- .............................................................................................................................................................................6-9
- ...........................................................................................................................................................................6-10
- ...........................................................................................................................................................................6-11
- ...........................................................................................................................................................................6-12
Delivery Schedule Splitting Rules ......................................................................................................................6-13
Assignment: Splitting Rules for Planning Delivery Schedule Instructions.........................................................6-14
Planning Delivery Schedules - Internal Delivery Schedules: Summary .............................................................6-15
Repetitive Manufacturing : Objectives ...............................................................................................................6-16
Make-to-Stock Repetitive Manufacturing - Scenario..........................................................................................6-17
Make-to-Stock Repetitive Manufacturing -Main Points .....................................................................................6-18
Make-to-Stock Repetitive Manufacturing - Master Data ....................................................................................6-19
Master Data in Make-to-Stock Repetitive Manufacturing : Material..................................................................6-20
Material Master: Repetitive Manufacturing Profile ............................................................................................6-21
Material Master: Production Versions ................................................................................................................6-22
Master Data in Make-to-Stock Repetitive Manufacturing : BOM ......................................................................6-23
Master Data in Make-to-Stock Repetitive Manufacturing : Production Line .....................................................6-24
Master Data in Make-to-Stock Repetitive Manufacturing : Routing ..................................................................6-25
Routing................................................................................................................................................................6-26
Run Schedule Header..........................................................................................................................................6-27
Integration of Controlling ...................................................................................................................................6-28
Make-to-Stock Repetitive Manufacturing - Planning .........................................................................................6-29
Creating a Master Plan ........................................................................................................................................6-30
Initial Screen for the Planning Table...................................................................................................................6-31
Planning Table / Period-Based Planning.............................................................................................................6-33
Planning in the Planning Table ...........................................................................................................................6-34
RS Dispatch List .................................................................................................................................................6-35
Make-to-Stock Repetitive Manufacturing - Controlling Material Flow..............................................................6-36
Make-to-Stock Repetitive Manufacturing - Backflushing ..................................................................................6-37
Backflushing .......................................................................................................................................................6-38
- ...........................................................................................................................................................................6-39
KANBAN: Objectives ........................................................................................................................................6-40
Production Processing: Contents.........................................................................................................................6-41
KANBAN ...........................................................................................................................................................6-42
The Kanban Card ................................................................................................................................................6-43
Business Management Environment for KANBAN ...........................................................................................6-44
KANBAN: Master Data......................................................................................................................................6-45
Supply Area ........................................................................................................................................................6-46
KANBAN Control Cycle ....................................................................................................................................6-47
Supply Sources in the KANBAN Procedure.......................................................................................................6-48
Excluding Materials from MRP ..........................................................................................................................6-49
General Procedure in KANBAN.........................................................................................................................6-50
Setting a Kanban to Empty .................................................................................................................................6-51
Setting Kanban to Full ........................................................................................................................................6-52
KANBAN Board.................................................................................................................................................6-53
- ...........................................................................................................................................................................6-54
MM Scheduling Agreement Processing: Unit Objectives.........................................................................................7-1
MM Scheduling Agreement Processing: Business Scenario.................................................................................7-2
- .............................................................................................................................................................................7-3
- .............................................................................................................................................................................7-4
MM Scheduling Agreement - Initial Screen .........................................................................................................7-5
- .............................................................................................................................................................................7-6
Control Data for Forecast Delivery Schedules......................................................................................................7-7
Procurement Process with Scheduling Agreements ..............................................................................................7-8
MRP ......................................................................................................................................................................7-9
Scheduling Agreement Releases .........................................................................................................................7-10
Release Creation .................................................................................................................................................7-11
Aggregation with the Release Creation Profile ...................................................................................................7-12
- ...........................................................................................................................................................................7-14
- ...........................................................................................................................................................................7-15
Cumulative Quantitites - Definition ....................................................................................................................7-16
Cumulative Quantitites - Examples.....................................................................................................................7-17
Reconciliation of Cumulative Quantities ............................................................................................................7-18
Releases for the Supplier.....................................................................................................................................7-19
Contract-Referenced Scheduling Agreement ......................................................................................................7-20
MM Scheduling Agreement Processing: Summary ............................................................................................7-22
Internet Scenarios: Unit Objectives...........................................................................................................................8-1
Internet Scenarios: Business Scenario...................................................................................................................8-2
Internet Scenario: Materials Management ............................................................................................................8-3
Internet: Integration of R/3 with External Catalogs ..............................................................................................8-4
Data Transferred ...................................................................................................................................................8-5
Scenario 1 for Procurement Using Catalogs:Intranet - Entire Data Processing Inside the Firewall .....................8-6
Scenario 2 for Procurement Using Catalogs:External Catalog .............................................................................8-7
Scenario 3 for Procurement Using Catalogs:R/3 Product Catalog........................................................................8-8
Internet Scenario: Sales and Distribution..............................................................................................................8-9
Sales and Distribution .........................................................................................................................................8-10
- ...........................................................................................................................................................................8-11
SAP’s Product Configurator ...............................................................................................................................8-12
Internet: Creating Sales Orders ...........................................................................................................................8-13
Internet Scenarios: Production Planning .............................................................................................................8-14
Production Planning (1): Internet KANBAN ......................................................................................................8-15
Production Planning (2) ......................................................................................................................................8-16
Internet Scenarios: Summary ..............................................................................................................................8-17
What’s Next in Automotive?: Unit Objectives .........................................................................................................9-1
Delivery Schedule Types for Scheduling Ageements ...........................................................................................9-2
Bordero: Definition ...............................................................................................................................................9-3
Bordero: Definition ...............................................................................................................................................9-4
Bordero: Aim of Process.......................................................................................................................................9-5
Bordero: Information Flow ...................................................................................................................................9-6
Bordero: Material Flow.........................................................................................................................................9-7
Packaging Logistics ..............................................................................................................................................9-8
- .............................................................................................................................................................................9-9
Package Administration (HUM) .........................................................................................................................9-10
Packing According to Packaging Instructions.....................................................................................................9-11
Customer-Specific Packing in Production ..........................................................................................................9-12
What’s New in Automotive? : Summary ............................................................................................................9-13
Exercises .................................................................................................................................................................10-1
- ...........................................................................................................................................................................10-2
- ...........................................................................................................................................................................10-3
- ...........................................................................................................................................................................10-6
- .........................................................................................................................................................................10-10
- .........................................................................................................................................................................10-12
- .........................................................................................................................................................................10-14
- .........................................................................................................................................................................10-19
Solutions .................................................................................................................................................................11-1
- ...........................................................................................................................................................................11-2
- ...........................................................................................................................................................................11-3
- ...........................................................................................................................................................................11-8
- .........................................................................................................................................................................11-13
- .........................................................................................................................................................................11-17
- .........................................................................................................................................................................11-20
- .........................................................................................................................................................................11-27
IAU210 SAP: Automotive: Supplier
IAU210
SAP: Automotive:
Supplier
 SAP AG 1999
IAU210 SAP Automotive: Supplier

June 1998
Beta0
50024833
Copyright
Copyright 1998 SAP AG. All rights reserved.
Neither this training manual nor any part thereof may

be copied or reproduced in any form or by any means,
or translated into another language, without the prior
consent of SAP AG. The information contained in this
document is subject to change and supplement
without prior notice.
All rights reserved.
 SAP AG
Trademarks
SAP and the SAP logo are registered trademarks of SAP AG.
MS-DOS and EXCEL are registered trademarks of Microsoft.
OS/2, CICS, MVS, ACF/VTAM, VSE, AIX, OS/400 and AS/400 are registered trademarks of IBM.
X Window System is a registered trademark of MIT University.
SINIX, UTM and BS2000 are registered trademarks of Siemens.
UNIX is a registered trademark of AT&T.
HP-UX is a registered trademark of Hewlett Packard.
DECnet, DECstation, DECsystem, VAXstation and VMS are registered trademarks of DEC.
Ethernet is a registered trademark of the Xerox Corporation.
ORACLE SQL*net, SQL*+ PRO*C are registered trademarks of the ORACLE Corporation.
INFORMIX-OnLine and INFORMIX-ESQL/C are registered trademarks of the INFORMIX
Corporation.
Target Audience
Members of automotive supplier project teams, for

example:
Procurement specialists
Sales & distribution specialists
Material requirements planners
Computer personnel
The following courses are prerequisites for the IAU210

course: LO020, LO050, LO150 und LO235. Participation
in other level 2 and level 3 courses in related areas is
recommended, as is a basic knowledge of and
experience in the supplier industry.
R
 SAP AG
Note to the user

The training materials are not teach-yourself programs. They complement the course instructor's
explanations. Space is provided on each page for you to make notes on this additional information.
R/3 Integration Model
SD FI
Sales & Financial
Distribution Accounting
MM CO
Materials Controlling
Mgmt
PP AA
R/3
Production Asset
Planning Accounting
QM
Quality
Client/Server PS
Project
Mgmt PM
Plant
ABAP WF
System
Maintenance Workflow
HR IS
Human Industry
Resources Solutions
 SAP AG
The SAP R/3 System continues to set new standards for universal standard software. Based on
progressive development techniques, the SAP R/3 System allows comprehensive integration of
business administration and data processing.
The SAP R/3 System components are characterized by comprehensive business functions with the
most modern technology. The integration of the applications ensures that all the functions are directly
available in the system and thus in the enterprise.
Curriculum Path Automotive 1
Level 2 Level 3
LO050 5 Days
Manufacturing Planning
LO020 4 Days LO235 2 Days

Procurement Processes KANBAN
LO150 5 Days
Customer Order
Management IAU210 3 Days
SAP Automotive:
Supplier
 SAP AG
Curriculum Path Automotive 2
Level 2 Level 3
LO050 5 Days
Manufacturing Planning
IAU220 3 Days
SAP Automotive:
LO020 4 Days Original Equipment
Procurement Processes Manufacturer
IAU230 1 Day
LO150 5 Days SAP Automotive:
Customer Order Aftermarket l
Management
 SAP AG
Course Contents
SD: Scheduling Agreement Processing (Inbound
Processing)
SD: Delivery / Shipping / Billing
MM: Evaluated Receipt Settlement,
FI: Credit Memo Procedure, Payment
SD: Processing With an External Service Agent
PP: Repetitive Manufacturing / KANBAN
MM: Scheduling Agreement Processing (Outbound
Processing)
Internet Scenarios
What’s next in R/3-Automotive? R
 SAP AG
Contents
Preface
Unit 1 Introduction Unit 6 Production
Unit 2 SD Scheduling Agreement Unit 7 MM Scheduling Agreement

Processing Processing
Unit 3 Shipping Activities Unit 8 Internet: Overview
Unit 4 Billing, Credit Memo Procedure Unit 9 What’s Next in Automotive?
Unit 5 Scheduling Agreement

Processing With an ESA
Exercises
Solutions R
 SAP AG
IAU210 Introduction: Contents
Overview of the automotive logistics chain
Overview of the EDI procedure
 SAP AG
(C) SAP AG IAU210 1-1

IAU210 Introduction: Course Goals
This course will enable you to understand business

processes which are typical of the automotive supplier
industry and are covered in the R/3 industry solution SAP
Automotive
The course gives you a preview of planned developments
for the automotive environment.
 SAP AG

IAU210 Introduction: Course Objectives
At the conclusion of this unit, you will be able

to:
Discuss the automotive logistics chain, with and
without the integration of an external service agent
Explain the EDI procedure using the IDoc interface
Assign the message types supported under Release

4.0B to business processes.
 SAP AG

IAU210 Introduction: Business Scenario 1
This scenario shows typical business

processes used by an automotive OEM and
supplier. Special emphasis is laid on
communications between OEM and tier 1
suppliers, as well as suppliers on other
levels. The quantity and value flow is
explained.
 SAP AG

IAU210 Introduction: Business Scenario 2
Starting from the OEM‘S MM scheduling

agreement, forecast and JIT delivery
schedules are sent via EDI to the suppliers.
The suppliers deliver against the JIT
delivery schedules and bill the deliveries
(internally). The OEM carries out evaluated
receipt settlement and executes a payment
run, dispatching credit memo and payment
advice notes.
The supplier carries out production using
repetitive manufacturing / KANBAN. In this
example, procurement is demonstrated
using scheduling agreements.
R
 SAP AG

The Automotive Logistics Chain: Objectives

to:
Describe the automotive logistics chain, with and

without the integration of an external service agent.
 SAP AG

Complete Logistics System for Networked
Value-Added Chains
Planning
E E
Strat.
V D D C
U
E I I S
Planning
N
Operat.
Supplier Tier 1 Vehicle Dealer T

D supplier Manufacturer O
O M
R E
R
Control
Value-added
process
From raw material to consumer
 SAP AG

Automotive Logistics Chain: Levels 1
OEM
Supplier
(tier 1)
Subsupplier
(tier 2)
R
 SAP AG

O.E.M.
External
service agent
Supplier
(Tier 1)
Subsupplier
(Tier 2) R
 SAP AG
The external service agent (ESA) has a consignment warehouse, from which he delivers to the OEM.
Other functions can be carried out by the external service agent, such as:
set creation
packing sets for assembly
assembling items
repackaging
The ESA‘s activities can be settled using the MM service billing function.

Business Process Without External Service
Agent 1
Goods recipient Supplier of goods
Sched. agt
schedule line
 SAP AG
For this example, we assume that a goods recipient (for example, an O.E.M.) has made a scheduling
agreement with a supplier of goods (supplier). The computer systems of goods recipient and supplier
communicate via EDI.

Agent 2
Goods recipient Forecast delivery sched. (DELINS) Supplier of goods
Sched. agt SD sched. agt
schedule line schedule line
(forecast
delivery schedule)
 SAP AG
For this example, we assume that a goods recipient (for example, an O.E.M.) has made a scheduling
agreement with a supplier of goods (supplier). The computer systems of goods recipient and supplier
communicate via EDI.
Forecast delivery schedules are dispatched monthly via EDI. They are relevant for planning, but not for
delivery.

Agent 3
)
Sched. agt JIT delivery sched. (DELINS)) SD sched. agt
Delivery
GI
 SAP AG

Agent 4
Sched. agt JIT delivery sched. (DELINS) SD sched. agt
Shipping Shipping notification (DESADV) Delivery

notification
GI
Goods receipt Invoice
Accounting
document
 SAP AG

Agent 5
)
Sched. agt. JIT delivery sched. (DELINS)) SD sched. agt
Shipping Shipping notification (DESADV) Delivery

notification
GI
Goods receipt
Invoice
ERS
Accounting
Credit memo (GSVERF)
Invoice document
Update
Accounting
doc. 1
R
Accounting document 1: open item
 SAP AG

Agent 6
MM sched. agt JIT delivery sched. (DELINS) SD sched. agt
Shipping notification (DESADV)
Shipping Delivery
Delivery
notification
InvoiceGI WA
Goods receipt Invoice
Accounting
ERS document
Accounting
document
Update
Invoice
Update
Accounting
doc. 1 Payment advice note (REMADV)
Payment Payment advice
run note
Accounting R
doc. 2 Accounting document 1: open item

Accounting document 2: payment
 SAP AG

Notes on System Example
Manufacturer (Sapsota AG) and supplier

(Compumotive Ltd.) are both in the same R/3 client.
Communications are transmitted via the IDoc interface
with transactional RFC. There is no EDI subsystem
(converter).
 SAP AG

Business Process With External Service Agent
Goods recipient Forecast del. sched. (DELINS) Supplier of goods
schedule line JIT ESA schedule line
Consignment
delivery
fill-up
sched. Delivery
(DELINS) (DESADV)
Delivery note ESA withdrawal

Delivery note
(EDLNOT)
Goods receipt (DESADV) Delivery for ESA
withdrawal
GI
Credit memo Credit memo (GSVERF) Invoice
Accounting Accounting doc.

doc 1
Payment advice note (REMADV)
Accounting Update
doc. 2 Paymt advice note
R
Accounting document 1: open item
Accounting document 2: payment
 SAP AG

Process Overview for Supplier
Sched. agmt Sales planning Materials mgt
Customer Purchasing (purch.
FDS order, sched. agmt)
JDS Inventory mgt
Demand management Invoice verification,
credit memo
MRP procedure
Flexible shop floor control

Prod. by lot size Repetitive mfg Make-to-order prod.
Time scheduling Rate-based planning Customer-order-oriented
Production order Run schedule headers processing
Work centers Production lines Production order
Work centers
KANBAN / JIT
Shipping R
Invoice
 SAP AG

The Automotive Logistics Chain: Summary
In this topic, you have covered

The different levels of the automotive logistics chain.
Automotive business processes in general
SD / MM procedures with and without an external service agent
Production
 SAP AG

Overview of EDI Procedure: Objectives

to:
outline the EDI procedure using the IDoc interface.
assign to business processes the message types

supported under Release 4.0B.
 SAP AG

Terminology
EDI
Electronic Data Interchange
Procedure for the automatic interchange of
structured business documents.
IDoc
Intermediate Document
Instrument for realization of interfaces.
 SAP AG

R/3 EDI Procedure - Starting Point
OEM Tier 1 supplier Tier X supplier
Document Document
R/3 system
 SAP AG

R/3 EDI - SD Procedure
Document
EDI system R/3 system
IDoc IDoc
External
EDI subsystem
Specific standard R
EDI messages
 SAP AG

R/3 EDI - MM Procedure
Document
R/3 system EDI system
IDoc IDoc
External
EDI subsystem
Specific standard R
EDI messages
 SAP AG

R/3 EDI Procedure
Document Document
EDI system R/3 system EDI system
IDoc IDoc
External
EDI subsystem
Specific standard Specific standard R
EDI messages EDI messages
 SAP AG

EDI Scenario for Supplier (Extract) 1
SAP R/3
EDI interface (IDoc interface) for SD
IDoc IDoc IDoc

Forecast or IDoc IDoc IDoc
Delivery Shipping Credit invoice Payment
JIT DS notification advice note
order memo
(MAIS) (FI)
EDI subsystem
 SAP AG

EDI Scenario for Supplier 2
SAP R/3
EDI interface (IDoc interface) for MM
IDoc IDoc IDoc IDoc

Forecast or Credit IDoc Payment
Shipping Invoice
JIT DS notification memo advice note
(FI)
EDI subsystem
 SAP AG

Overview of EDI Standards
Message type VDA Odette Edifact Ansi. Misc. R/3
X.12 message
type
Forecast delivery sched. 4905 DELINS DELFOR 830 DELINS
JIT delivery schedule 4915 DELINS DELJIT 862 DELINS
Delivery order Subset DELJIT GM DELORD

(inbound
processing)
Delivery note and 4913 AVIEXP DESADV 856 DESADV

transport data
Credit memo 4908 INVOIC DEBADV 820 GSVERF
Debit memo 4908 INVOIC DEBADV 820 GSVERF
Payment advice note 4907 REMADV REMADV 820 REMADV
 SAP AG

EDI Procedure: Summary

The EDI procedure using IDocs, independent of standards.
The EDI messages supported by SAP.
The conversion of logical message types to specific standards.
 SAP AG

IAU210 Introduction: Summary
This unit gives you an overview of the automotive logistics

chain as reproduced in R/3. It describes the communication
flow between the various levels on the chain:
OEM
Supplier (tier 1)
Subsupplier (tier X)
Within R/3, EDI communications between these levels are

carried out using message types which are independent of
standards. Using an EDI subsystem, these are then
converted into EDI messages of a specific standard type.
 SAP AG

SD Scheduling Agreement Processing:
Contents
SD Scheduling Agreements
Delivery Orders
 SAP AG

SD Scheduling Agreement Processing: Unit
Objectives
to:
Outline the structure of a scheduling agreement and
create scheduling agreements.
Create and set the basic controls for forecast and JIT
delivery schedules.
Explain the sales process using cumulative
quantities.
Describe the process of determining scheduling
agreements for inbound delivery schedules.
Explain the use of delivery orders (MAIS procedure)
as an alternative to JIT delivery schedules.
 SAP AG

SD Scheduling Agreement Processing:
Business Scenario
OEM and suppliers agree on scheduling
agreements to represent a long-term
customer-supplier relationship.
The customer dispatches forecast delivery
schedules to the supplier for planning
purposes.
The supplier receives the customer’s JIT
delivery schedules and delivery orders,
which are relevant for delivery.
 SAP AG

SD Scheduling Agreements: Objectives
At the conclusion of this topic, you will be

able to:
list the basic elements of inbound forecast and JIT
delivery schedules.
outline the structure of a scheduling agreement and
create scheduling agreements and schedule lines.
create a packing proposal in the scheduling
agreement.
create and set the basic controls for forecast and JIT
delivery schedules
explain the sales process using cumulative
quantities (delivery schedules)
describe the process of determining a scheduling
agreement for an inbound delivery schedule.
R
 SAP AG

Business Process (Section)
Sched. agt JIT delivery sched. (DELINS) SD sched. agt
 SAP AG
This example is based on the following scenario:

The goods recipient transmits a monthly forecast delivery schedule (FDS) per EDI to the supplier of
goods. The supplier of goods uses it for MRP.
JIT delivery schedules (JDS) are transmitted on a daily basis, again per EDI. In the example, the JIT
delivery schedule is set as relevant for delivery, but not for MRP.

SD Scheduling Agreement - General
Scheduling
Scheduling agreement
agreement
1.4.98
1.6.99
 SAP AG
Definition
Outline agreement created for one or more materials, containing the quantity of material that a customer
expects to require over a certain period of time.
Use
The scheduling agreement is used as a basis for delivery of a material. The customer regularly transmits
forecast delivery schedules in order to schedule delivery of a certain quantity of materials.

SD Scheduling Agreement - Main Points
Administration of various types of schedules

(forecast, JIT and planning delivery schedules)
Receipt of delivery schedules per EDI
SchedAgt
SchedAgt Updating of delivery schedule histories
Monitoring of changes
1.4.98
1.6.99 Use of cumulative quantities
Correction delivery notes
Automatic fiscal year change
Entering of packing proposals
 SAP AG
Planning delivery schedules are not relevant to the business scenario in this unit and are covered in the
unit on Repetitive Manufacturing.

SD Scheduling Agreement - Initial Screen
Document types (extract)

SSA : Scheduling agreement with delivery schedule
SAEX: ESA scheduling agreement
SchedAgt
SchedAgt LZM : Scheduling agreement with delivery order
1.4.98 Organizational levels

1.6.99
Sales organization mandatory
Distribution channel levels
Division
Sales office optional
Sales group levels
 SAP AG
This section deals with scheduling agreements with document type “SSA”.

SD Scheduling Agreement - Structure
Header
Kopf
Header
Kopf Customer:
Kunde:
Kunde: 5401
Customer: 5401
Customer:
5401
5401
Position
Item
Position
Item Material:
Material: 4712
4712
Formation
Historienbildung
of history
Delivery
Abrufe Forecast DS 55
Lieferabruf JIT DS
Feinabruf 25 25
schedules
Schedule lines
Einteilungen 41.1998 75 05.10.98 30
42.1998 90 06.10.98 20
... 07.10.98 25
12.10.98 ...
....
 SAP AG
You can create several scheduling agreement items under one header. However, SAP recommends that
you use only one item per header. This is the more common procedure and also allows for a better
overview, system performance and error processing.
Each delivery schedule contains schedule lines, which are logged in the history together with the
delivery schedules.

Types of Delivery Schedule
Forecast delivery schedule (for example, monthly quantities)

Weekly or monthly
J F M A ... quantities
JIT delivery schedule (for example, daily quantities)
01 02 03 04 05 06 07 08 09 ... Daily quantities
 SAP AG
Forecast delivery schedules are generally less precise than JIT delivery schedules. They are therefore
mainly used for planning and MRP, while JIT delivery schedules are generally relevant for delivery.

Relevance of Schedules for Delivery and MRP
Planning Del.Sch.
type
FDS
A JDS
FDS
B
JDS
FDS
C
JDS
FDS
D JDS
FDS
E JDS
JDS Horizon t
Key: Schedule line
R
Delivery schedule
Area of schedule relevant for MRP
Area of schedule relevant for delivery
 SAP AG
Examples:
You set the MRP indicator “E” if the goods recipient works without JIT delivery schedules. The forecast
delivery schedule is then relevant not only for MRP but also for delivery.
For this example, “C” is set, making the forecast delivery schedule relevant for MRP and the JIT
delivery schedule relevant for delivery.
MRP indicator “B” means that

- within the JIT delivery schedule horizon, the JIT delivery schedule is relevant for MRP and delivery,
and
- out with the JIT delivery schedule horizon, the forecast delivery schedule is relevant for MRP and
delivery.

Creating Forecast and JIT Delivery Schedules
OEM Supplier
Forecast DS Forecast DS 8
MRP run 8 JIT
JITDS
Lieferabruf
DS 7
40
40
daily
Feinabruf
39
Lieferabruf
Feinabruf
39 6
21.3
21.3
38
Schedule 38
Feinabruf
21.2
Feinabruf
21.2
lines weekly 21.3
21.3
21.2
JIT
JIT delivery
delivery 21.2
Planning of schedules
sched
sched lines
lines Forecast delivery schedules
JIT delivery schedules
JIT
JIT DS
DS
40 MRP run
40
Production
 SAP AG
Forecast and JIT delivery schedules are usually received from the OEM per EDI.
Manual creation of forecast and JIT delivery schedules is allowed.
In most cases, several generations of forecast and JIT delivery schedules must be administrated.

Administrating Generations of
Schedules
New schedule replaces older schedule (forecast
del.sched./forecast del.sched. and JIT del.sched./JIT
del.sched.)
You can compare generations as desired
FDS / FDS
FDS / JDS
JDS / JDS in a table and in a graphic
Example:
Example: FDS 1 FDS 2
Date Qty CQ Date Qty CQ

01.07. 1000 1000 01.07. 1500 1500
01.08. 2000 3000 01.08. 1000 2500
01.09. 1000 4000 01.09. 2000 4500
01.10. 1000 5000 01.10. 1000 5500
 SAP AG
Exceptions to the above replacement rule:
Contrary to the above replacement rule, the customer can, if desired, mix new schedules with old. In
order to do this the customer must, however, set a special indicator in the schedule.
For VDA 4915 JIT delivery schedules, the special indicator is the MRP status key. The value that the
customer sets for this indicator is displayed in the JIT delivery schedule header.
If the MRP status key has value “B”, the older forecast delivery schedule lines that fall before and after
the validity period of the new schedule are copied to the new schedule. Otherwise, the new schedule
completely replaces the older one.
For Odette delivery schedules the special indicator is the forecast delivery schedule key. This
indicator is not displayed.
If the forecast delivery schedule key has value “1”, the older schedule lines that fall before the validity
period of the new schedule are copied to the new schedule. Otherwise, the new schedule completely
replaces the older one.

Monitoring Changes
Tolerance days: 10 Change of date

Tolerance qty: 100 pc. Change of quantity
Tolerance % rate: 20 % Change of quantity
Pieces
500 new
400
∆ ∆ old
300
∆
200
∆
100
R
10 20 30 40 50 60 70 Days
 SAP AG
Percentage/quantity tolerance applies if one of the two is contained in the delivery schedule.
Percentage rate quantity change refers to cumulative quantities. Quantity tolerance is therefore usually
used in the short term, and percentage tolerance in the long term.

Cumulative Quantities - Definition
The monitoring of sales / procurement operations

between business partners
Customer Vendor
!!
??
 SAP AG

Cumulative Quantities - Examples
Σ Σ Σ
Examples:
Cumulative received quantity (CRecQ)
Sum of all delivery quantities received by the customer
in the customer‘s fiscal year.
Cumulative delivered quantity (CDQ)
Sum of all delivery quantities made in the
customer‘s fiscal year.
Σ Σ Σ .
Cumulative released quantity (CRelQ)
Sum of the cumulative quantities received by the
customer, and the schedule line quantities up to
the relevant deadline.
 SAP AG

Cumulative Quantities - Quantity Adjustment
Initial situation
CRecQ = 1000
CDQ = 1200
CDQ - CRecQ = 200 (“quantity in transit”)
Quantity adjustment after receipt of delivery schedule

DATE Release Qty Open CRelQ
Forecast 2.1. 500 300 1500

del.
del.sched.
sched. 9.1. 500 500 2000
JIT del. 2.1. 50 - 1050

sched.
sched. 3.1. 50 - 1100
4.1. 100 - 1200
5.1. 100 100 1300
R
6.1. 100 100 1400
 SAP AG
The system determines the “open” quantities by calculating the difference between delivery schedule
quantities and quantities in transit. For example, since there is a quantity in transit of 200 pieces, R/3
regards the first 3 JIT delivery schedule lines are as delivered.

Supplier Go-Aheads
Material go-
go-ahead
current cumulative material go-
go-ahead quantity (current
(current CMGQ)
maximum cumulative material go-
go-ahead quantity (max
(max.. CMGQ)
Repetitive Mfg Production go-

go-ahead
Prod.
current cumulative production go-ahead quantity (current CPGQ)
Line
maximum cumulative production go-
(max.. CPGQ)
Delivery go-
go-ahead
current cumulative delivery go-
go-ahead quantity (current
(current CDGQ)
maximum cumulative delivery go-
(max.. CDGQ)
R
 SAP AG
Cumulative material go-ahead quantities and cumulative production go-ahead quantities (current
and maximum) are stored in the forecast delivery schedule header, cumulative delivery go-ahead
quantities in the JIT delivery schedule header.

Correction Delivery Note
Correction delivery notes when introducing R/3 SD

scheduling agreements
Correction of cumulative delivered quantities at any point in
time if differences with customer arise
Correction:
Correction: - 200 pc on 14. 07.
Delivery note Date Qty CDQ

1 05.07. 100 100
2 10.07. 200 300
4711 14.07. - 200 100
3 15.07. 100 200
4 20.07. 200 400
5 30.07. 300 700
 SAP AG

Automatic Fiscal Year Change 1
July 98
Mon Tue Wed Thu Fri Sat Sun
1 2 3 4 5 Cumulative quantities generally reset at
6 7 8 9 10 11 12
13 14 15 16 17 18 19 end of fiscal year
20 21 22 23 24 25 26
21 28 29 30 31
You know when a new fiscal year has

started
if the OEM enters the figures set to zero on date in
the IDoc
by reading the customer‘s CRecQ on receipt of the
EDI delivery schedule, if no figures set to zero on
date is transmitted
 SAP AG
Cumulative quantities are usually reset to zero at the end of the year. This year is not necessarily the
calendar year. The fiscal year change is automatically registered on receipt of the EDI (Electronic Data
Interchange) delivery schedule. The end of the fiscal year is defined in the fiscal year variant field in the
customer record for the goods recipient (marketing view). If this field is not maintained, the system
assumes that the fiscal year ends on the 31.12.

Example (no figures set to zero date,
July 98
Mon Tue Wed Thu Fri Sat Sun no quantity in transit)
1 2 3 4 5
6 7 8 9 10 11 12
13 14 15 16 17 18 19 End of fiscal year 97: 31.7.98
20 21 22 23 24 25 26
21 28 29 30 31
Date of delivery schedule 24.7.98
FY = 97
CDQ (97) = 1000
CRecQ = 1000
The customer sends a delivery schedule to the
supplier in fiscal year 97. Its cumulative received
quantity matches the cumulative delivered
quantity from 97.
The customer is in fiscal year 97.
 SAP AG

July 98
1 2 3 4 5
6 7 8 9 10 11 12
20 21 22 23 24 25 26
21 28 29 30 31 Date of delivery schedule 6.8.98
FY = 98
CDQ (97) = 1000
CDQ (98) = 100
CRecQ = 1100
quantity matches the sum of cumulative delivered
quantities from 97 and 98.
The customer has not yet closed fiscal year
97. R
 SAP AG

July 98
1 2 3 4 5
6 7 8 9 10 11 12
20 21 22 23 24 25 26
21 28 29 30 31
Date of delivery schedule 10.8.98
FY = 98
CDQ (97) = 1000
CDQ (98) = 100
CRecQ = 100
quantity matches the cumulative delivered
quantity from 98.
The customer has now closed fiscal year 97.
R
 SAP AG

Packing Proposal
A customer packing proposal and a rounding quantity

can be entered in the scheduling agreement.
The system proposes this data when the delivery is
processed.
 SAP AG

Manual Determination of Scheduling
Agreement
Purchase
Purchase order
order number
number
Customer
Customer material
material number
number
Sold-
Sold-to party
Sold-to party
Scheduling
Partner
Partner description
description agreement or
selection list
Unloading
Unloading point
point
Usage
Usage
Description
Description
Delivery
Delivery
 SAP AG
Existing forecast delivery schedules can be found using the search help shown above.

Automatic Determination of Scheduling
Agreement for Delivery Schedule
Step 1
Determination of sold-to party for EDI FDS/JDS in
accordance with Customizing
Vendor
Vendor no.
no..
no
Partner
Partner description
description Sold-
Sold-to party
Sold-to party
Unloading
Unloading pt
pt (optional)
(optional)
If a single sold-to party cannot be determined:
Error!
 SAP AG
The forecast or JIT delivery IDoc contains fields for the customer's vendor number for the supplier, the
plant to be delivered to, and the unloading point.
Use this information to determine the customer number in a table. You enter the plant to be delivered to
in R/3 in the field, “Partner description”. If the determination goes wrong, the IDoc basis system sends a
mail to the appropriate personnel.
To maintain this table in Customizing, select the following path:
Sales and Distribution/Sales/Sales Documents /Scheduling Agreements with Delivery Schedules
/Control Incoming EDI for Scheduling Agreements/ Assign sold-to party for delivery schedules

Step 2
Optional selection criteria corresponding to your
entries in Customizing:
General data
Check PO no. X PackMaterials

CheckUnPt X TextNoPackQt.
Texts
 SAP AG
You can define the purchase order number (closing number) and the unloading point as additional
selection criteria in a Customizing table.
To maintain this table, select the following path in Customizing:
Sales and Distribution/Sales/Sales Documents/Scheduling Agreements With Delivery Schedules
/Control EDI Inbound Processing/ Define Special Features for Delivery Schedules.

Step 3
IDoc Matchcode
?
Closing
Closingno.
no.
no. optional PO
POno.
no.
no.
Error!
Cust.
Cust. material
Cust. material Cust.
Cust. material
Cust. material
Vendor
Vendor no.
no.
no.
Plant SchedAgt
SchedAgt
Plantto
to be
bedel.
del.
del. Sold-
Sold-to party
Sold-to party
Unloading
Unloadingpt
pt
1.4.98 OK
Plant
Plantto
to be
bedel.
del.
del. Partner
Partner desc.
desc.
desc. 1.6.99
Unloading
Unloading pt
pt optional Unloading
Unloading pt
pt
SchedAgt
SchedAgt
Usage
Usage Usage
Usage SchedAgt
SchedAgt
SchedAgt
SchedAgt
1.4.98
Description
Description Description
Description SchedAgt
SchedAgt
1.4.98 1.6.99 Error!
1.4.98 1.6.99
1.4.98 1.6.99
1.6.99
 SAP AG
The online search and the automatic determination of scheduling agreement for inbound delivery
schedule take place simultaneously.
The ”optional” beside closing number and unloading point means, “according to the optional selection
criteria set in Customizing”.

Error Processing
person responsible notified automatically

per e-mail
manual rework allowed
 SAP AG
If, for example, the system finds several possible scheduling agreements for a delivery schedule, the
person responsible can assign it manually.

SD Scheduling Agreement Processing :
Summary
In this topic, you have covered:
Basic elements of inbound forecast and JIT delivery schedules.

Scheduling agreement structure and creating scheduling agreements
and schedule lines.
Packing proposal in the scheduling agreement.
Control of forecast and JIT delivery schedules.
Monitoring of sales process using cumulative quantities.
Determination of SD scheduling agreements for inbound delivery
schedules.
 SAP AG

Delivery Orders: Objectives

able to:
Outline the general procedure for using delivery
orders.
Describe the differences between
scheduling agreements with document types LZM and SSA
delivery orders and JIT delivery schedules
Create scheduling agreements for the delivery order

procedure.
Create delivery orders.
 SAP AG

Delivery Order Procedure
SchedAgt
SchedAgt SchedAgt
SchedAgt SchedAgt
SchedAgt
Mat.-1 Mat.-2 Mat.-3
1.4.98 1.4.98 1.4.98

1.6.99 1.6.99 1.6.99
 SAP AG
The customer and the supplier have existing outline agreements, in this case scheduling agreements for
the delivery order procedure.

Delivery Order Procedure 1
SchedAgt
SchedAgt SchedAgt
SchedAgt SchedAgt
SchedAgt
1.4.98 1.4.98 1.4.98

1.6.99 1.6.99 1.6.99
Order
Order
Pick-up sheet Order
Order
Mat.-1 Mat.-1
Mat.-1
Mat.-2
Mat.-2
Mat.-1 Auslieferungs-
Auslieferungs-
Mat.-2 auftrag
Auslieferungs-
Auslieferungs
Mat.-3 -
Mat.-2
Mat.-3 auftrag
Auslieferungs-
Auslieferungs-
Mat.-3
Mat.-3
auftrag
Delivery order
 SAP AG
On the basis of these scheduling agreements, the customer prepares data for the delivery and transmits it
in a pick-up sheet. The supplier’s EDI subsystem receives the inbound pick-up sheet and converts it
into an IDoc (Intermediate Document). This is stored in the R/3 system. The supplier creates a delivery
order based on the IDoc. The data in the delivery order either comes from the IDoc or is manually
copied from the pick-up sheet. The system uses this data to determine the corresponding scheduling
agreement and creates order lines in the delivery order according to the quantities desired by the
customer.

Delivery Order Procedure 2
SchedAgt
SchedAgt SchedAgt
SchedAgt SchedAgt
SchedAgt
1.4.98 1.4.98 1.4.98

1.6.99 1.6.99 1.6.99
Order
Order
Pick-up sheet Order
.1
Order a d. pt Delivery 1
Unlo - Mat.-1
Mat.-1 Mat.-1 Forwarding
Mat.-1 agent
Mat.-2
Mat.-2
Auslieferungs-
Un
Mat.-2 auftragload. pt. 2
Auslieferungs
Mat.-3 -
Mat.-3 auftrag
Auslieferungs-
Auslieferungs-
Mat.-3
Mat.-3
auftrag
Delivery order Delivery 2

- Mat.-2
- Mat.-3
R
 SAP AG
The supplier creates one delivery per customer unloading point. These deliveries can be brought
together for one shipment. The customer's forwarding agent collects the materials at the agreed time.
There is generally only one unloading point per pickup sheet.
The delivery is invoiced.
The customer pays, making reference to the pick-up sheet number in the invoice.

Pick-Up Sheet
Pick-up Sheet
External customer document with function

similar to JIT delivery schedule
Mat.-1
Mat.-2
Addressee: supplier and forwarding agent
Mat.-3
Basis for delivery order

Contains one or more materials, from one
or more scheduling agreements, to be
delivered on the same date
 SAP AG
The pick-up sheet is like the customer's shopping list.

R/3 at present only supports inbound administration of pick-up sheets at the supplier.

SD Scheduling Agreement (Repeat)
Document types (extract)

SSA : Scheduling agreement with delivery schedule
SAEX: ESA scheduling agreement
SchedAgt
SchedAgt LZM : Scheduling agreement with delivery order
1.4.98
Organizational levels
1.6.99
Sales organization mandatory
Distribution channel levels
Division
Sales office optional
Sales group levels
 SAP AG
This section deals with scheduling agreements for delivery orders (document type ”LZM”).

Scheduling Agreements for Delivery Orders
Header
Header Customer:
Customer: 5401
Customer: 5401
Item
Item Material:
Material: 4712
4712
SchedAgt
SchedAgt
Del.
Del. scheds Forecast DS 5 Formation of history
1.4.98
1.6.99
Schedule lines 05.10.98 75

12.10.98 90
...
 SAP AG
The system automatically sets the planning indicator to “E” (no JIT delivery schedules).

Delivery Orders - Structure
Order Header
Pick-up date, time from/to
Item
Item 10
10
Del.
Del. Ord.
Ord. Material number
Sched
Sched line
line 11 Confirmed quantity/date
Item
Item 20
20 Material number
Sched
Sched line
Sched
Sched line
 SAP AG
Usually, each delivery order item has exactly one order line. Several order lines can only result from the
availability check.

Delivery Orders - Main Points 1
Invoice
Invoice
Pick-Up sheet
18.12.98
Pick-up date automatically taken as
delivery and pricing date.
SchedAgt
SchedAgt
Order Mat.
Mat.11
Mat.1
Mat.2 SchedAgt
SchedAgt
1.4.98
Mat.
Each item must refer to an LZM
Mat.22 1.6.99
scheduling agreement.
Ausl.
Ausl.-Auftr.
Auftr. 1.4.98
1.6.99
 SAP AG

Delivery Orders - Main Points 2
Order SchedAgt
SchedAgt
Mat.1 Mat.
Mat.11
Mat.2 CRecQ
1.4.98
1.6.99
Cumulative quantities are
Delivery Ord. based on delivery orders, not
CRelQ
on deliveries
+
No delivery tolerances allowed
-
Order
Del. Ord. Settlement of reqmts between

scheduling agreement, delivery
SchedAgt
SchedAgt order and delivery
R
1.4.98
1.6.99
Reqmts situation
 SAP AG

Delivery Orders: Summary
The general procedure for using delivery orders.

The differences between
scheduling agreements with document type LZM and
SSA.
delivery orders and JIT delivery schedules.
Creation of scheduling agreements for the delivery order
procedure.
Creation of delivery orders.
 SAP AG

Shipping Activities: Contents
Overview of Shipping
Delivery
Picking (Lean Warehouse Management)
Packing
Shipment
Goods issue
Shipping notification
 SAP AG

Shipping Activities: Unit Objectives

to:
Describe the basic steps in delivery
processing
Delivery
Packing
Shipment
Goods issue
 SAP AG

Shipping Activities: Business Scenario
Based on the JIT delivery schedule dates,

you create deliveries with reference to the
SD scheduling agreement. The delivery
quantities and dates are sent to the goods
recipient in a shipping notification.
 SAP AG

Shipping Activities: Business Process (Section)
Goods recipient Forecast del. sched. (DELINS) Supplier of goods
Sched. agt. JIT del. sched.(DELINS) SD sched. agt
Shipping notification (DESADV)) Delivery
GI
 SAP AG
Based on the (JIT) delivery schedule dates, you create deliveries with reference to the SD scheduling
agreement. You inform the goods recipient of delivery quantities and dates in a shipping notification.

Shipping Overview Diagram
Reference activity: for example, sched. agt
Shipping Delivery creation
Delivery
processing Picking
Delivery Business
interface partner/
External
Packing system
Goods issue
 SAP AG

Messages in Shipping
Delivery note
LD00 Quality inspection
Shipping
notification issue indicator
LAVA LQCA, LQCB
Material tag
Message
Message type
type ODEL
Label
Packing list Shipping unit
PL00 0001
Freight list
LL00 R
 SAP AG
A message is a type of communication that supports the exchange of information between you and your
partners.
Messages can be sent from various objects (for example, delivery, group of deliveries, shipping unit).
You can create the delivery note and packing list on the basis of the delivery, the loading list on the
basis of a group of deliveries.
You can set various criteria for message determination. This is known as the condition technique and
allows you flexible control. This technique is also used to determine the attributes of the message, for
example:
the way the message is transmitted (transmission medium, such as printout, fax, EDI)
at what time the message is created (transmission time-spot)
to whom the message is going (partner/partner role)
for printouts, on which printer the message is printed
The system differentiates between item and header messages in deliveries. A header message refers to
the whole document (for example, delivery note). An item message can be created per document item
(for example, inspection certificate).
You can print labels or appendages for shipping units.
Sample forms for the messages contained in the standard system are shipped as standard, and can be
modified to suit the specific needs of your company.

Delivery
processing Picking
Delivery Business
interface partner/
external
Packing system
Goods issue
 SAP AG

Shipping Point Determination
Shipping Shipping point Possible

Loading group Plant
condition (proposed) shipping points
Fork- 1100
01 1000 1000
lift 1200
Sold-to party/
Material Order item
Order
 SAP AG
You define a shipping point responsible for each scheduling agreement item. The system puts forward a
proposal automatically, which you can change within given limits.
The choice of shipping point depends on the following criteria:
issuing plant, determined per forecast delivery schedule item
requests to shipping (for example, express) - represented in the field ”shipping condition”
loading equipment required - represented in the field ”loading group” in the material master
If you have maintained a sales document type, the system proposes the shipping condition specified
there. Otherwise the system takes the shipping condition from the master record for the sold-to party.
A delivery always goes out from one specific shipping point. The shipping point for a delivery cannot be
changed.
When a scheduling agreement is delivered via a shipping point, only the scheduling agreement items
designated for that shipping point are copied into the delivery.

Route Determination in Sales Documents
Where
Where from?
from? How?
How? What?
What? Where
Where to?
to?
Country/
Country/ Shipping Transportation
Transportation Route
Departure zone conditions group
zone
Sold-to party/ Goods

Shipping point Material
Order recipient
 SAP AG
Route determination in the scheduling agreement item depends on:

the country and departure zone of the shipping point (assigned in Customizing)
the shipping condition agreed with the sold-to-party
the transportation group assigned to the material
the country and transportation zone of the goods recipient (assigned in the customer master record)
According to these criteria, you can enter in a table the routes to be determined by the system.
In the scheduling agreement item, you can manually overwrite the route determined by the system.

Delivery
processing Picking
Delivery Business
interface partner/
external
Packing system
Goods issue
 SAP AG

Delivery Structure
For example, shipping point

Header route, ship-
ship-to party
For example., material,

Item 1 qty, order reference
Item 2
Item 3
 SAP AG
The delivery consists of a header and an unlimited number of items.

Delivery
processing Picking
Delivery Business
interface partner/
external
Packing system
Goods issue
 SAP AG

Picking
Delivery item
not relevant for picking: relevant for picking:

services, texts... components...
Trigger picking
- using WM/Lean WM (transfer order) Notify subsystem
- using SD (picking request)
R
 SAP AG
Picking is the process of preparing goods for delivery to the customer with special attention paid to
dates, quantity and quality.
You specify for each item category whether it is relevant for picking.
Picking is often carried out using a printed pick list. SAP recommends using the Warehouse
Management (WM) transfer order functions for this. You do not need to install the complete Warehouse
Management system; Lean Warehouse Management is sufficient.
Using delivery message control, you can copy data to a susbsystem that is set for picking (see unit on
delivery interfaces).
The system is set as standard so that all items that are relevant for picking must be picked before the
goods issue can be posted. In other words, delivery quantity and pick quantity must agree.

Picking with WM/Lean WM: Process
Delivery
Transfer order
Print transfer order
Confirm transfer Only when

order confirmation
compulsory!
Delivery items
Process differences
complete
Adopt picking quantities Create new transfer order

R
(partial delivery) for quantity difference

 SAP AG
WM picking is carried out by creating a transfer order. This document initiates and monitors movements
within a warehouse complex. Based on the items in a delivery that are to be picked using WM, one or
more transfer orders are created, according to warehouse conditions.
The transfer order is then printed. You can do this manually or set the system to do it automatically.
As an alternative to printing the transfer order as a pick list, you can transfer the transfer order data to a
non-SAP system with portable data capture or to a warehouse control unit.
In confirming the transfer order, you confirm the quantities withdrawn from the warehouse. You can
also confirm variance quantities here. It is also possible to work without confirmation requirement, in
which case you can also enter variance quantities.
In case of incomplete picking, you can either initiate subsequent picking by creating a new transfer
order, or copy the picked quantities into the delivery as delivery quantities, so that goods issue can be
posted.

Confirming Transfer Orders
Delivery
Delivery Pick Pick Status Status

qty qty status WM act. WM act.
10 M1 10 pcs 10 pcs C B C
20 M3 20 L 20 L C B C
Transfer Transfer
order was order must
created be
confirmed
Confirmation
 SAP AG
When you create the transfer order, the system sets the delivery quantity as the picking quantity so that
the picking status is set to C (= fully picked).
If you wish to have the system record the fact that the picking procedure is complete, you can set the
confirmation requirement.
You must confirm the transfer order and therefore also the picked quantities (field „Pick qty“) before the
goods issue is posted.
If you have organized your warehouse so that picking causes changes to the delivery in only a limited
number of cases, and the confirmation takes place on time, you can limit this step to the deliveries to be
changed and also work without the confirmation requirement.
During confirmation, it is possible to report differences in quantities. You can record the cause for the
difference in the system by entering a difference indicator.
As soon as confirmation is complete, the status of the WM activities is set to C, regardless of the
confirmed quantity. The amount of the pick quantity only influences the picking status.

Delivery
processing Picking
Delivery Business
interface partner/
external
Packing system
Goods issue
 SAP AG

General Requirements for Packing
There are three categories of packaging material:
Supplier-owned packaging material
Customer-owned packaging material
Disposable packaging material
Each category must be entered in the material master

in R/3, using appropriate material types.
le
er
r
ab
lie
m
pp
os
o
st
sp
Su
Cu
Di
 SAP AG
R/3 can monitor stocks of packaging materials via the material master.
Three typical types of packaging materials are:
returnable packaging, supplier-owned
returnable packaging, customer-owned
disposable packaging

Shipping Materials and Shipping Units
Shipping materials
Box Basket Container Truck
Shipping units
Packing Shipping unit
Material
M1 1 pc
Material M1 1 pc
M2 5 pc M3 5 pc
 SAP AG
In packaging, we use the terms “shipping materials” and “shipping unit”.

Shipping materials are materials that are used to pack goods.
A shipping unit is a package that results from the packing of goods in shipping materials.
Shipping units can be packed again. This is referred to as “multi-level packing”.
Authorized shipping materials are defined in Customizing.

Packing Shipping Units
Delivery C1
C1 Pallet
Pallet 11
Container
Container 11
C2
C2
Pallet
Pallet 11
C3
C3
C4
C4
 SAP AG
Packing is the process of assigning delivery materials to shipping materials. The resulting shipping units
may then be packed in additional shipping materials, thereby forming new shipping units.
You can use as many levels as required (multi-level packing).
After an item has been packed, the system updates the packing status for each item in the delivery, for
example ‘partially packed' or ‘fully packed'.
A material must be relevant for packing, and so identified on the material master.

Packing in Orders, Deliveries, and Shipments
Order
Order
Copy requirements
Delivery
Delivery
Packing requirements:
e.g. no packing when there
is a credit block
Shipment
Shipment
 SAP AG
The packing function is available:

in orders (as packing proposals)
in deliveries
in shipments
The packing proposal in the order can be copied to the delivery. You control this in the copy control
table for deliveries.
By making the appropriate settings in Customizing, you can require that certain conditions be met before
packing in the delivery can be carried out. In the standard version, packing cannot be carried out when
the delivery has been blocked by the credit check.

Managing Stock for Shipping Materials
Delivery 80000637
10 Material 1 100 PC Pack:

Material 1 on
20 Pallet 5 PC pallet
The system generates an item

for the shipping material
VERP LEIH Item category group in the shipping

material
Billing of the Returnable packaging R
shipping mat. processing
 SAP AG
You may need to manage stock for shipping materials. To this end, you can set the system to generate an
item with the corresponding quantity in the delivery for the shipping materials.
To automatically generate items for shipping materials:
You must set item category determination in Customizing. In this context, table entries with PACK
usage are relevant.
The delivering plant must be determined using the plant determination rule in the shipping material
type or must be entered manually.
You can bill the customer for the shipping materials, or you can use returnable shipping materials that
are not billed.
In the first case, you must create the shipping materials in the material master record with item
category group VERP. The item category determination procedure in the standard system determines
item category DLN. These items can then be copied to the billing document.
You must create returnable shipping materials in the material master record with item category group
LEIH (item category TAL is determined). When goods issue is posted, the materials are transferred
to special stock for the customer (or special stock partner, e.g. the forwarding agent). These items
will not be copied to the billing document.
Note: In subsequent processing of returnable packaging, use order type returnable packaging pickup
(LA) then returns delivery (RE). Or, if the packaging is kept by the customer, order type returnable
packaging issue (LN) then billing.

Supplier-Owned Packaging Material
Material type “VERP“
Material group used for reporting purposes
Item category group “LEIH”
Standard cost
r
lie
pp
Su
 SAP AG
Setting up a supplier-owned returnable packaging material in R/3 requires certain settings:

The material type is “VERP.” This is a standard R/3 material type.
Under “General data” in the “Sales: sales organization data 1” view in the material master, enter a
material group for returnable packaging. This is for evaluation and sorting purposes.
Under “Grouping terms” in the “Sales: sales organization data 2” view, select the item category
group “LEIH” to designate the material as supplier-owned returnable packaging. You may need to
verify the item categories are correctly defined for deliveries by starting a new session and going to
“Define delivery item category determination in deliveries” under “Sales and Distribution”,
“Shipping”, “Deliveries” in Customizing.
The “LEIH” item category group must be assigned to the item category “TAL”.
In the “Sales: general/plant data” view under “Packaging material data”, enter a reporting/sorting
value for material group:shipping materials. Also, enter a shipping material type, which is required to
designate this as a packaging material in SD shipping.
In the “MRP 2” view, enter a special procurement type designating the packaging material as a
consignment material.

Customer-Owned Packaging Material
Create new material type “ZCON” copied from “VERP”

Modify type to track quantity but not value
er
om
st
Cu
 SAP AG
Setting up a customer-owned returnable packaging material in R/3 requires certain settings:

In Cutomizing, create the material type “ZCON” an. This is a user-defined material type, copied from
VERP and modified so that quantities are tracked, but not valued for costing. The result is that there are
Materials Management (MM) transactions, but no general ledger (G/L) entries.
In the Material Master data, enter a reporting/sorting value for material group/shipping materials. Also,
enter a shipping material type, which is required to designate this as a packaging material in SD
shipping.

Disposable Packaging Material
Materialart “VERP”
Shipping material type entry required
Item category group “VERP”
Disposable packaging material can be billed
ag ble
g
ck sa
in
pa spo
Di
 SAP AG
Setting up a disposable packaging material in R/3 requires certain settings:

The material type is “VERP.” This is a standard R/3 material type.
Under “Packaging material data” in the “Sales: general/plant data” view, enter a shipping material type,
which is required to designate this as a packaging material in SD shipping.
Select item category group “VERP” to designate disposable packaging materials.

Receiving Returnable Packaging Materials:
Which Transaction?
To receive customer-owned packaging, create a MM
goods receipt, movement type 501
To receive your supplier-owned packaging back, create
a sales order type “LA”
Goods Receipt (501)

er
m
o
st
Cu
d er
or
es
r
lie
Sal
pp
A”
Su
“L
R
 SAP AG
In R/3, you typically receive goods by creating a goods receipt. Use this process to receive customer-
owned returnable packaging. Select goods receipt movement type 501 for this case.
However, to receive your own returnable packaging back, you must create a sales order type ”LA,”
which acts as a return order. Then, create a return delivery, type ”LR,” referencing the sales order to
complete the process.
The end result of both processes is that inventory records are updated.

Delivery
Picking
processing Delivery Business
interface partner/
external
Packing system
Transportation
Goods issue
 SAP AG

Delivery Restriction - Shipment
Delivery Shipment
for example, stop-off shipment
one D1
shipping Mannheim
point Delivery 1
Heidelberg
L2 D1
Delivery 1+2
one
Route Heilbronn
D1
Delivery 1
one R
goods recipient Stuttgart

 SAP AG
Warehouse and shipping point activities are supported in the R/3 delivery using a “shipping operation”.
You can also use the delivery itself to create a simple transport procedure.
Basically, a delivery goes out from a certain shipping point, takes a certain route, and arrives at a certain
customer. This fact is also reflected in the delivery itself, where these three criteria are header fields.
If you load several deliveries onto one truck and include several shipping points and goods recipients in
this one truckload, it is advisable to use the R/3 transport functions. They allow you to summarize
deliveries by criteria of your choice into one document, the shipment.
Functions for transportation planning and processing and shipment costs are covered in the course
LO611.

Shipment Documents and their Functions
Drawing together
deliveries /shipping
notifications in one rt
shipment po Ser
ans vic
ft r ea
deo ge
Creating shipping M o nt
papers and
messages Recording shipment
characteristics
Functions of a
shipment doc.
Recording planned
and actual dates / Determining stages
status data of shipment
A C
Plnd Act.
Representing
shipping unit B
 SAP AG
The shipment document is central to processing shipments in R/3. It contains all the information
necessary to organize and carry out the shipment.
It fulfills the following functions:
compiling delivery notifications for inbound shipments
compiling deliveries for outbound shipments
assigning service agents, mode of transport, shipment type, and so on
time scheduling and monitoring
entry of stages of shipment
cross-delivery packing and representing shipping units
creation of messages and shipping papers
recording of shipment-relevant texts
recording of partner information

Packing and Loading for Shipment
Delivery D1
Shipping unit 1
M1 1 pc
M2 5 pc
Shipping unit 3
Delivery D2
M3 2 pc
Shipping unit 2
 SAP AG
Within the shipment, you can pack deliveries or pack existing shipping units further. For example, with
delivery items that are already packed into boxes, you can pack them into further containers and load
them onto a truck. The functions supporting this are basically the same as those used for packing in the
delivery.
Characteristics of packing in the shipment:
cross-delivery packing
any packaging from the delivery is copied and cannot be changed
shipping materials cannot be generated as delivery items; it is impossible to use inventory management
for shipping materials.
To transmit a delivery notification from the shipment, you must set message determination for message
type LAT1.

Bearbeiten
Lieferung Picking
Delivery Business
interface partner/
external
Packing system
Goods issue
 SAP AG

Goods Issue
Shipping point
Maayy
M
7
4 5 6
1 2 3 14
11 12 13 1
8 9 10 20 2
18 19
15 16 17 28
23 24 25 26 27
22
29 30 31 Delivery 11
Goods issue
 SAP AG
Posting goods for a delivery completes shipping activities.

After goods issue has been posted, there is limited scope for changing the delivery. In particular, no
changes can be made to the quantities. At this point in processing, the delivery document has to reflect
the actual physical delivery.
Goods issue can be posted for single delivery. Alternatively, you can display the deliveries currently
being processed in order to select all deliveries for which goods issue is due to be posted. In this way a
single transaction can be used to post goods issue for several deliveries.
When you are processing a single delivery, you can specify the effective goods issue date without
changing the planned date. Do this, you select Edit -> Actual goods issue date in the quantity overview
screen for the delivery. A dialog box appears in which you enter the actual goods issue date. You can
post goods issue for this date using Post goods issue. The corresponding goods issue document is then
posted with the actual goods issue date.
If no explicit specifications are made for the goods issue date, the current date is taken as the goods issue
date.
Goods issue applies to the whole delivery.
Any errors are logged, e.g. when data is incomplete or when picking has not been carried out fully for
the items.

Effects of Goods Issue
KM
T
A A Delivery
Text
Goods issue
K1
M1 100 pc
Sett. price 12 DM
Reqmt
Article M1
Stock
Account 1 Stock
SchedAgt
Angebot X X
B
Delivery
Billing R
due list
 SAP AG
Possibilities for changing a delivery are restricted by goods issue posting, notably in that quantities can
no longer be changed. The delivery must reflect the facts exactly.
The goods issue:
reduces warehouse stocks
posts changes in value to the balance sheet accounts in inventory accounting
reduces delivery requirements
sets status information in the delivery
is recorded in document flow
creates the worklist for billing
If you use the transaction ”Create billing document” to carry out billing before goods issue, you can set
the system to do this via copying control in Customizing.

Delivery
processing Picking
Delivery Business
interface partner/
external
Packing system
Goods issue
 SAP AG

Delivery Communication Requirements
Forwarding
agent
Notification to forwarding agent,

message type: CANO
Shipping
confirmation (EDI)
Customer Vendor Service agent
Shipping notification, Shipping order,
message type: LAVA message type: SHOR
 SAP AG
If your shipping and transport operations involve working with business partners or external systems,
you need to exchange delivery information with these partners or systems. The communication medium
used for this is usually EDI.
The shipping notification notifies the customer of the delivery.
With the notification to forwarding agent, you transmit delivery data to your forwarding agent, enabling
them to pick up and deliver the goods.
The shipping order and shipping confirmation are for communications with a stockkeeper or service
agent, who manages the warehouse and is responsible for shipping the goods. The stockkeeper or
service agent either manages final delivery himself, or uses a forwarding agent.

Shipping Activities: Summary
You are now familiar with the basic steps for

delivering JIT delivery schedules:
Delivery
Packing
Shipment
Goods issue
 SAP AG

Billing, Credit Memo Procedure: Contents
Billing
Evaluated receipt settlement, credit memo procedure, payment
 SAP AG

Billing, Credit Memo Procedure:
Unit Objectives

to :
Describe a delivery-related billing document.
Enter goods receipt (at the customer) with reference

to the shipping notification, and describe automatic
goods receipt settlement with dispatch of credit
memo per EDI, and its effect at the supplier.
Reconstruct the payment run (at the customer) with
dispatch of the payment advice note, and its effects.
 SAP AG

Billing, Credit Memo Procedure: Business
Scenario
For delivery of the JIT delivery schedule
line, an “internal“ billing document is
created.
The goods recipient posts a goods receipt
with reference to the shipping notification,
settles it using the evaluated receipt
settlement (ERS) procedure, creates a
credit memo, and dispatches it per EDI to
the supplier. The credit memo is processed
at the supplier.
The goods recipient periodically executes
a payment run, and dispatches a payment
advice note per EDI to the supplier. R
 SAP AG

Billing: Objectives

able to:
Create the billing document for the delivered
schedule lines.
 SAP AG

Business Process (Section)
Goods recipient Delivery schedule (DELINS) Supplier of goods
Sched.agt. JIT del. schedule (DELINS SD sched.agt
Shipping notification Shipping notification (DESADV) Delivery
GI
Goods receipt
Billing doc.
GR
process
Accounting
Invoice document
Update
Accounting
document 1
Payment run Payment advice
Accounting note
document 2
R
Accounting doc. 1: Open item
Accounting doc. 2: Payment
 SAP AG

Structure of the Billing Document
The header contains information on
Header the invoice as a whole, for example:
conditions
partners
Item 1 texts
messages
commercial data, for example,
Item 2 conditions of payment valid for the
entire billing document
The items contain information on the

materials being billed, for example:
conditions
texts
partners
commercial data
 SAP AG

Effects of Billing Document Creation
When an billing document is
created:
bill. doc.
Customer‘ Receivable. accounting documents are created
credit
account
automatically, and G/L accounts
X
are updated
document flow and the status are
updated in all associated sales
Financial Sales Information System
100
90
statement and delivery documents
80
the customer‘s credit management

70
60
50
account is updated
40
30
20
10
0
Delivery
the statistics for the sales
1 2 3 4 5 6
Order
information system are updated

controlling elements like the
financial statements and profit
center billing document are
updated
R
 SAP AG

Options for Creating Invoices
Invoice
Invoice
Order
Order Delivery
Delivery
Invoice split
Invoice
Invoice
Delivery
Delivery Invoice
Invoice
Separate invoices Scheduling
Scheduling
per delivery agreement
agreement Delivery
Delivery Invoice
Invoice
Order
Order Delivery
Delivery
Delivery
Delivery
Collective invoice Invoice
Invoice
Order
Order Delivery
Delivery
 SAP AG

Billing: Summary
In this topic, you have created a delivery-related billing

document for a delivery schedule.
 SAP AG

Evaluated Receipt Settlement, Credit Memo
Procedure, Payment: Objectives
able to:
Describe goods receipt (at the customer) with
reference to the shipping notification.
Carry out evaluated receipt settlement with dispatch
of credit memo per EDI.
Describe the effect of the credit memo at the
supplier.
Reconstruct the payment run (at the customer) with
dispatch of the payment advice note and its effect at
the goods recipient.
 SAP AG

Goods Receipt
Purchased Goods
(vendor to customer)
Shipping
Shipping Packing
Notification
Notification Slip
GR with ref.
ref. GR with
to shipping reference
notification to a PO
 SAP AG
Goods receipt with reference to a shipping notification

Receipt of shipping notification from supplier
Receipt of goods from supplier
Posting of goods receipt
Goods receipt with reference to a purchase order
Receipt of packing slip from supplier
Verification that delivery has a purchase order reference
Posting of goods receipt

Information Contained in a Shipping
Notification
The shipping notification from the vendor contains
several pieces of information:
Customer number, vendor number, customer part number
Net quantities
Purchase Order (PO) number
Brut and net weight
Date and time
 SAP AG

Automatic Goods Receipt Settlement
Vendor
Vendor
Release Invoice
Verwendungs-
100 pcs Goods receipt Verwendungs-
entscheid
on 31.12. 100 pcs. entscheid
Credit
Credit memo
memo
per
per EDI
EDI
Company
Company
Invoice
 SAP AG

Automatic Payment Program
Del.-
Del.- Basic
Basic data
data Parameters
Parameters Inv.
Inv.
master Doc
Recomm.
Recomm. run Processing
Processing
recom-
recom-
mendation
mendation
Payment run
Print run
Payment
overview
Überweisung
Payment
Payment
advice
advice note
note
per
per EDI
R
EDI
 SAP AG

Evaluated Receipt Settlement, Credit Memo
Procedure, Payment: Summary
entering goods receipt with reference to shipping notification.

carrying out the ERS process.
dispatching and receiving credit memos, and their effects.
executing the payment run, dispatching the payment advice
note, and its effects.
 SAP AG

Scheduling Agreement Processing With an
External Service Agent: Unit Objectives
to:
Describe the difference between the
business processes with and without an
ESA.
Maintain ESA scheduling agreements.
Describe inventory management of
consignment stock.
Describe inventory management of
returnable packaging.
 SAP AG

Scheduling Agreement Processing With an
External Service Agent: Business Scenario
The customer sends forecast delivery
schedules to the supplier, who in turn
delivers to the ESA (consignment fill-up).
The ESA receives JIT delivery schedules
from the customer, makes the deliveries,
and informs the supplier accordingly.
The supplier posts the consignment
withdrawal and bills it.
 SAP AG

O.E.M.
External
service agent
Supplier
(Tier 1)
Subsupplier
(Tier 2) R
 SAP AG
The external service agent (ESA) has a consignment warehouse, from which he delivers to the OEM.
Other functions can be carried out by the external service agent, such as:
set creation
packing sets for assembly
assembling items
repackaging
The ESA‘s activities can be settled using the MM service billing function.

Business Process with External Service Agent 1
Goods recipient Forecast DS (DELINS) Supplier of goods
schedule line ESA schedule line
 SAP AG

schedule line ESA Consignment schedule line
fill-up
Delivery
 SAP AG

fill-up
Delivery
JIT DS
(DESADV)
(DELINS)
 SAP AG

JIT DS fill-up
(DELINS) Delivery
(DESADV)
Delivery note Delivery note ESA withdrawal

(DESADV) (EDLNOT)
Goods receipt Delivery for ESA
withdrawal
GI
Bill
 SAP AG

MM sched. agt SD sched. agt
JIT DS fill-up
(DELINS) Delivery
(DESADV)

(DESADV) (EDLNOT)
withdrawal
GI
Credit memo (GSVERF) Bill
Credit memo
Accounting
document
Accounting Document 1: open item

R
 SAP AG

MM sched. agt SD sched. agt
JIT DS fill-up
(DELINS) Delivery
(DESADV)

(DESADV) (EDLNOT)
withdrawal
GI
Credit memo (GSVERF) Bill
Credit memo
Accounting Accounting
Document 1 Document
Accounting Update
Document 2 Paymt advice note
Accounting Document 1: open item R
Accounting Document 2: payment
 SAP AG
The ”PO number” field in the ESA order (ESA withdrawal) contains the delivery note number of the
delivery note sent from ESA to customer. This enables you to assign the customer's bill and credit
memo.

EDI Data Flow: Shipping Via External Service
Agents
Forecast delivery schedule (1)
Credit memo (5)
Component
Payment advice note (6)
supplier Customer
Delivery note Delivery note JIT delivery

(2) (4) schedule (3)
Delivery note (4)
Forwarding
agent
ESA
 SAP AG

Scheduling Agreement Elements
Difference between ESA and other standard agreements (SSA)
Sales document type “SAEX”

Item type “LKN”
Partner functions in the document header:
Sold-to party Customer

Bill-to party Customer
Payer Customer
Special stock partner External service agent
Ship-to party External service agent
R
 SAP AG
The scheduling agreement sales document type is set to ”SAEX”

Assign the partner functions as follows in the document header:
- The O.E.M. is the sold-to party, bill-to party and payer.
- The external service agent is the special stock partner and the ship-to party.

Scheduling Agreement Elements (2)
Scheduling agreement transfer
Forecast delivery schedules are sent from O.E.M. to supplier.
JIT delivery schedules are sent from O.E.M. directly to external
service agent.
Additional cumulative quantities:
Withdrawal cumulative quantity

(total quantity delivered by ESA to customer
in one fiscal year)
Cumulative scheduled quantity withdrawal
(from the last delivery by
external service agent to customer as per FDS)
 SAP AG
Example:
The O.E.M. dispatches forecast delivery schedules for the ESA scheduling agreement weekly to the
supplier. The JIT delivery schedules are dispatched daily by the O.E.M. to the ESA, who delivers in
accordance with the JIT delivery schedules.
Two additional cumulative quantities are used to define this business process:
Withdrawal CQ: states the total quantity supplied to the customer by an external service agent
in the ongoing fiscal year.
CSQ withdrawal: states the cumulative withdrawal quantity for the last delivery sent by the
external service agent to the customer (as per customer's last forecast
delivery schedule).

Delivery to the External Service Agent
(Consignment Fill-Up)
When processing a delivery on the basis of an SAEX
scheduling agreement, material is delivered to an
external service agent.
Picking
Packaging
Delivery
Post
goods issue Delivery to ESA
(to consignment
Shipping
stock)
notification
to ESA R
 SAP AG
In delivery processing, deliveries are created for the ”SAEX” scheduling agreements.

Notes on Packaging Materials
Nonreturnable packaging
le
in ab
ag rn
Is handled as with normal shipping
or
g
c k tu
nd
pa nre
Returnable packaging v.
Ve
No
Is handled as special stock
Manual stock transfers must be used to send it from
external service agent to customer
Manual transfers
3
of special stock
2
Goods issue
1
from normal
stock to special
stock R
 SAP AG
Returnable packaging is posted as special stock when delivered to the external service agent.
On receipt of delivery note from external service agent and posting of goods issue to the customer, you
use a two-step procedure to carry out the stock transfer of returnable packaging from consignment stock
to returnable packaging stock at customer.

Delivery from External Service Agent to
Customer
The following are created along with the external
service agent‘s shipping notification (EDLNOT):
Sales order (ED) / Delivery (LF)
The following manual entries are required:
Posting the goods issue (consignment withdrawal)
Creating a billing document
(for internal accounts receivable)
ED
sales order Post
(delivery) goods Billing
Deliver to
customer issue document
(accounts
R
receivable
 SAP AG
On receiving the JIT delivery schedule from the customer, the ESA delivers the goods to the goods
recipient from consignment stock.
The customer is informed per shipping notification of the consignment withdrawal. This information is
simultaneously transmitted to the supplier per EDLNOT. The supplier then posts the consignment
withdrawal.
The customer pays the billing documents based on the shipping notification.

Scheduling Agreement Processing with an
External Service Agent: Summary
When using an ESA to deliver to a customer,
a scheduling agreement with document type
“SAEX” is required.
The ESA receives the goods in accordance
with the forecast delivery schedule
(consignment fill-up), and delivers against the
customer’s JIT delivery schedules.
The component supplier posts the
consignment withdrawal, and bills it.
 SAP AG

Production Processing: Contents
Planning Delivery Schedules - Internal Delivery Schedules
Repetitive Manufacturing
KANBAN
 SAP AG

Production Processing: Unit Objectives

to:
Use the planning delivery schedules as an interface
between Sales and Distribution and Material
Requirements Planning.
Explain make-to-stock repetitive manufacturing.
Use KANBAN as an alternative for controlling

material flow.
 SAP AG

Production Processing: Business Scenario
The requirements for the inbound forecast delivery

schedules are edited into planning delivery
schedules and passed to MRP.
They are produced using repetitive manufacturing.
Component stocks are replenished using KANBAN.
 SAP AG

Planning Delivery Schedules - Internal Delivery
Schedules: Objectives
able to :
maintain planning delivery schedules.
convert forecast delivery schedules into planning

delivery schedules using the planning delivery
schedule instruction.
 SAP AG

SD Scheduling Agreement - Structure With
Planning Delivery Schedules
Header
Header Customer:
Customer: 5401
5401
Item
Item Material:
Material: 4712
4712
Del. schedules Forecast DS 5 JIT DS 25 Planning DS 7

History formation
05.10.98 10
Lines 41.98 50 05.10.98 20
06.10.98 10
42.98 90 06.10.98 10
07.10.98 10
... 07.10.98 10
08.10.98 10
08.10.98 10
09.10.98 10
12.10.98 ...
....
....
 SAP AG
Planning delivery schedules can be utilized as an interface between sales and MRP. They allow you to
edit the forecast delivery schedules (customer data!) for purposes of MRP and, where appropriate,
shipping.

Functions of the Planning Delivery Schedule
Internal delivery schedule for planning
St
requirements:
t
Planning which have not yet been covered by forecast delivery schedules
which the customer has not communicated in sufficient detail
independently of imprecise or unreliable forecast delivery schedules
before any forecast delivery schedules have been received at all
Replaces the forecast delivery schedule in terms

of planning relevance
Delivery Can replace the forecast delivery schedule in

terms of delivery relevance
 SAP AG

Planning Delivery Schedule - Overview
Internal
Other data,
such as
sales plan Planning P
delivery l
M Forecast a
A delivery Manual or schedule
EDI n
N schedule automatic
U W.42.1998 - 100 generation as per n
12.10. - 20
F W.43.1998 - 100 planning delivery i D
schedule 13.10. - 20
W.44.1998 - 100
A instruction 14.10. - 20 n E
C 15.10. - 20 g L
T JIT 16.10. - 20
delivery 19.10. - 100 I
U EDI schedule 26.10. - 100 V
R
12.10. - 20
E 13.10. - 20
E
R 14.10. - 21 R
15.10. - 19 Y
16.10. - 20 R
 SAP AG

Planning Delivery Schedule Instruction
Planning
Planning DS
DS instruction
instruction D
DBB TT Val
Val PP A
A Description
Description
Delivery relevance Description

cription
Base date Validity Schedule line Automatic

1 = Release date period transfer generation
2 = Date from old DS
generation
Date type
2 = Weeks
3 = Months
 SAP AG

Planning Delivery Schedules with Automatic
Generation
Planning
Planning DS
DS instruction
instruction D
DBB TT Val
Val PP A
A Description
Description
XX 11 33 55 XX XX Example
Example
Forecast
Forecast DS
DS 11 Planning
Planning DS
DS 11
generate
automatically
01.06.98 30 01.06.98 30
Lines 01.07.98 20 01.07.98 20
01.08.98 25 01.08.98 25
01.09.98 15 01.09.98 15
01.10.98 15 01.10.98 15
Base date : 01.06.98

R
 SAP AG
When a forecast delivery schedule is created or received via EDI, the system automatically generates a
planning delivery schedule.

Planning Delivery Schedules with Manual
Generation
Planning
Planning DS
DS instruction
instruction D
DBB TT Val
Val PP A
A Description
Description
XX 11 33 55 XX Example
Example
Forecast
Forecast DS
DS 22 Planning
Planning DS
DS 22
generate
manually
01.06.98 30 01.06.98 30
Lines 01.07.98 20 01.07.98 20
01.08.98 25 01.08.98 25
01.09.98 15 01.09.98 15
01.10.98 15 01.10.98 15

R
 SAP AG
The system creates a planning delivery schedule for the last forecast delivery schedule if you explicitly
instruct it to do so.

Planning Delivery Schedules with Date and
Quantity Alterations
Planning
Planning DS
DS instruction
instruction D
DBB TT Val
Val PP A
A Description
Description
Example
Forecast
Forecast DS
DS 33 Planning
Planning DS
DS 33
01.06.98 30 01.06.98 30
Lines 01.07.98 20 01.07.98 20
01.08.98 25 01.08.98
01.08.98 15
01.09.98 15 15.08.98 10
01.10.98 15 01.09.98 15
01.10.98 15
R
 SAP AG
You can change quantities and dates and create new schedule lines in an existing planning delivery
schedule.

Planning Delivery Schedules with Alteration of
Validity Period
Planning
Planning DS
DS instruction
instruction LL B
B TT Val
Val PP A
A Description
Description
Example
Forecast
Forecast DS
DS 44 Planning
Planning DS
DS 44
01.06.98 30 01.06.98 30
Lines 01.07.98 20 01.07.98 20
01.08.98 25 01.08.98 25
01.09.98 15
01.10.98 15

R
 SAP AG
Only those schedule lines that fall within three months after the base date are converted in the planning
delivery schedule.

Delivery Schedule Splitting Rules
Splitting Rules
are assigned to the planning delivery schedule instructions
define how forecast DS lines are split into planning DS lines
specify how to handle public holidays in the splitting
procedure
specify rounding procedures for splitting
Example
Split rule Mo Tu We Th Fr Sa Su F M Description
SD1 1 1 1 1 1 2 Equal distribution
SD2 2 2 2 2 1 1 Friday half capacity
SD3 1 2 Weekly reqmts
 SAP AG

Assignment: Splitting Rules for Planning
Delivery Schedule Instructions
More than one delivery schedule splitting rule can be
assigned to one planning delivery schedule instruction.
For the delivery schedule split of a forecast delivery
schedule line, the system uses:
a range of coverage which is valid for the date type of the schedule
line concerned
the shortest range of coverage that includes the schedule line deadline
Example:
Base date for planning DS generation is 2 April 1998, that is, the Thursday of CW 14
Date type Range Split rule Validity End-of-range date

2 (=Week) 008 SD1 Weeks -21.1998 24.05.1998
2 (=Week) 032 SD3 Weeks 22.-45.1998 08.11.1998R
3 (=Month) 002 SD1 Months .-05.1998 31.05.1998

3 (=Month) 007 SD3 Months 06.-10.1998 31.10.1998
 SAP AG

Planning Delivery Schedules - Internal Delivery
Schedules: Summary
Planning delivery schedules are “internal” delivery schedules,
used to pass on requirements to MRP and shipping.
They replace the planning-relevant and (given appropriate
identification) the delivery-relevant parts of the forecast
delivery schedule as well.
Conversion of a forecast delivery schedule into a planning
delivery schedule is controlled using the planning delivery
schedule instruction.
 SAP AG

Repetitive Manufacturing : Objectives

able to:
Maintain the basic master data for
Repetitive Manufacturing.
Assign planned orders to production lines
using the planning table and print out the
master plan for production.
Describe KANBAN as an alternative for
controlling material flow.
Carry out the backflush.
 SAP AG

Make-to-Stock Repetitive Manufacturing -
Scenario
Sched.
Sched. Agt
Agt
Navigation
Navigation
system
system
1.4.1998
1.6.2004
Make-to-stock
repetitive
manufacturing
Cable
Cable set
set CPU
CPU
Component
Component
replenishment
replenishment R
KANBAN
 SAP AG

Main Points
Run schedule quantities
Production
Time
line 1
Planning periods
Run schedule quantities

Production
Time
line 2
Planning periods
Planned orders only (run schedule quantities)

Production orders not necessary!
Period-based planning (planning periods)
R
 SAP AG

Master Data
11 Master Data
22 Planning: Lead Time Scheduling
33 Controlling Material
Supply Chain Flow
Execution
44 Backflushing
Supply Chain Planning
 SAP AG

Master Data in Make-to-Stock Repetitive
Manufacturing : Material
Material Repetitive
Repetitive manufacturing
manufacturing indicator
indicator and
and profile
profile
Materialmaster

master Production
record
Production versions
versions
record Accounting

Accounting // costing
costing
 SAP AG

Material Master: Repetitive Manufacturing
Profile
Contains control parameters for
repetitive manufacturing:
Goods issue Separation of goods issue
Reporting Pt 1
and/or activities
from goods receipt
Movement types
Goods issue
Reporting Pt 2 Reporting point procedure
...
Goods receipt
Goods storage
 SAP AG

Material Master: Production Versions
Production version 1
Routing
Material
master
- receiving storage location, assembly

- proposed issue storage location,
components
Describes production processes
 SAP AG

Manufacturing : BOM

Repetitive
manufacturing ind.
ind. and
and profile
profile
Material
Material master
master
Production
Production versions
versions

Accounting
Accounting and
and costing
costing
BOM
Planned
Planned material
material consumption
consumption
BOM Storage

Storage location for
location for backflush
backflush
 SAP AG

Manufacturing : Production Line

Repetitive
manufacturing ind.
ind. and
and profile
profile
Material
Material master
master
Production versions
Production versions

Accounting
Accounting and
and costing
costing
BOM Planned
Planned material
consumption
BOM
Storage
Storage location
location for
for backflush
backflush
Production Available
Available capacity
capacity
ProductionLine
Line Cost center
Cost center

 SAP AG

Manufacturing : Routing

Repetitive
manufacturing ind.
ind. and
and profile
profile
Material
Material master
master
Production versions
Production versions

Accounting
Accounting and
and costing
costing
BOM Planned
Planned material
consumption
BOM
Storage
Storage location
location for
for backflush
backflush
Production Available
Available capacity
capacity
Production Line
Line
Cost
Cost center
center
Routing
Routing Operations
Operations
Routing
Specification
Specification of
of production
production rate
rate (quantity/time)
(quantity/time)
R
 SAP AG

Routing
Organizational separation
Routing Routing - rate routing
Define the production rate

for capacity requirements
for scheduling
 SAP AG

Run Schedule Header
Routing
Material
master Copy at
creation
Run schedule header for production version 2

No tion
c d
du an
pro tities s
an ne
qu eadi Routing
d 23
22
21
Allows production of a material on a production line

for a certain period (technical object in the background)
R
 SAP AG

Integration of Controlling
Production Run schedule quantities

Material A
Material B
Planning periods Time
Controlling
Material A Production cost collector
Material B Production cost collector
Post periods Time
 SAP AG

Planning
11 Master Data
33 Controlling Material
Supply Chain Flow
Execution
44 Backflushing
Supply Chain Planning
 SAP AG

Creating a Master Plan
<
Demand Sales and
management Distribution
Requirements
MRP / MPS
Planning table
 SAP AG

Initial Screen for the Planning Table
Plant 1200
Period of examination
Start End Period
Selection by production line
Production line line3 ...
WkCtr hierarchy Nodes
Selection by materials
Material
Product group
Class Class type
MRP controller ...
Capacity planning/scheduling
X Capacity planning Prod./basic dates
Sched. strategy
R
 SAP AG
The planning table is displayed according to the selections you make in the initial screen. In order to
gain an overview of the complete production planned for one production line, you can access the
planning table via production line. To gain an overview of the complete production planned for a
specific material, you can select via material. You can plan all materials and lines which fall within the
responsibility of an MRP controller. it is also possible to access the planning table with a line
hierarchy and plan production on the bottleneck work center (this is the scheduling work center in the
work center hierarchy). To do this, you enter the work center hierarchy in the ”Selection by production
line” section.
The ”Line detailed selection” function sets the system to determine all materials for the production line
and check which other lines these materials could be produced on. .
if you select the Capacity planning field, the planning table displays capacity data for the given
production line. You can display capacity data stored at ”rate-based planning” or ”detailed planning”
level
If you work with MRP, you can use the ”Planning by MRP lists” function, as in the MRP list collective
display, to select specific materials with certain exception messages that have been determined in the
planning run, and then process these in the planning table.
If you want to access the planning table with the selection criteria ”Production line”, you must have
entered a work center (production line) in the production version. At least one operation should be
carried out at this work center in the routing.

Planning Table / Period-Based Planning
4.9.2001 In this section, you can
Capacity data EH due 5.9.2001
monitor the capacity utilization
Line 1 % 0 100 on the production lines
50
Required h 0 16 8
Available h 16 16 16
Line 2 % 0 0 150
Required h 0 0 24
Material data EH due 4.9.2001 In this section, you can

5.9.2001
assign the quantities to
Material A the production lines.
Reqmts pc 100 100
Available quantity pc 200 200 200
Production Line 1 pc 100 50
Production Line 2 pc 50 Assignment mode
Not yet assigned pc 0 0 0 R
 SAP AG

Planning in the Planning Table
Capacity data Un due 4.9.2001 In this section, you can:

Line 1
Required
%
h
0
0
100
16
50
8
- assign production quantities to
Available
Line 2
h
%
16
0
16
0
16
150
production lines
Required
Available
h
h
0
16
0
16
24
16 - enter new production quantities
Material data 4.9.2001
- increase production quantities
Un due
Material A - monitor capacity load utilization

Reqmts
Quantity available
pc
pc 200
100
200
100
200 on the production lines
Production Line 1 pc 100 50
Production Line 2 pc 50
Not yet assigned pc 0 0 0
In this section, you can process the following

receipts:
- planned orders
- production orders for discrete manufacturing
- process orders for process manufacturing
 SAP AG

RS Dispatch List
Capacity data Un due 4.9.2001
Line 1
Required
%
h
0
0
100
16
50
8
Work Distribution
Available
Line 2
h
%
16
0
16
0
16
150
List (Line1)
Required h 0 0 24
- Materials to be produced
Material data 4.9.2001
Material A
Un due
- Start of production: date & time
Reqmts
Available quantity
pc
pc 200
100
200
100
200
- End of production: date & time
Production line 1 pc 100 50 - Quantity to be produced
Production line 2 pc 50
Not yet assigned pc 0 0 0 - Unit of measure
- Order type and number
Sort criteria
 SAP AG

Controlling Material Flow
11 Master Data
33 Supply Chain
Controlling Execution
Material Flow
44 Supply Chain Planning

Backflushing
 SAP AG

Backflushing
11 Master Data
33 Supply Chain
Controlling Execution
Material Flow
44 Supply Chain Planning

Backflushing
 SAP AG

Backflushing
Goods receipt
posted
Motherboard
Production line
Material
Materialcosts
costs
posted
posted
Goods issue
posting Activity-
Activity-
Activity-
related
relatedcosts
costs
posted
posted
Production storage location PL03
Updated
Updated
BIOS Memory Processor LIS
LISstatistics
statistics
 SAP AG

Repetitive Manufacturing: Summary
In this topic, you have covered production using repetitive

manufacturing, in particular
Setting the master data
Carrying out planning in the planning table
Printing the list of run schedule quantities
Controlling material flow
Backflushing
 SAP AG

KANBAN: Objectives

able to :
Describe the business management environment for
KANBAN.
Set the master data for KANBAN.
Explain the general process flow of supplying

materials using KANBAN.
 SAP AG

Production Processing: Contents
Planning Delivery Schedules - Internal Delivery Schedules
Repetitive Manufacturing
KANBAN
 SAP AG

KANBAN
Demand source Supply source
Material
Kanban
 SAP AG

The Kanban Card
The card shows:

Material: 0000815
What is produced Quantity: 100 pc.
How much is produced
Manufacturer: 007
Where it is produced
Demand source: 088
How it is produced
Location: Shelf A014
Where it is delivered to Column 3
How it is transported Compartment 4
... Container: Wire basket
 SAP AG

Business Management Environment for
KANBAN
The supply source must deliver the material quickly
short setup times
no collection of Kanbans, but FIFO
availability of capacity and components
There should be a steady requirement for the material

Production must not take place in advance
(Production quantity = Kanban quantity)
Responsibility is shifted from central planning to the
shop floor
 SAP AG

KANBAN: Master Data
11 Master Data
22 General Procedure
 SAP AG

Supply Area
Supply Area 3
E
D Supply Area 2
Supply Area 1
B
Production
Assignment of storage location
Assignment of person responsible
R
 SAP AG

KANBAN Control Cycle
Demand source Supply source

•Supply Area • Person
responsible
Delivery • Vendor
• Issuing plant
• Warehouse
Control cycle
Requirement
The control cycle defines the relationship between the

supply source and the demand source.
R
 SAP AG

Supply Sources in the KANBAN Procedure
KANBAN
In-house
production
KANBAN
Shop floor
External
procurement
KANBAN
Stock transfer
Demand source Supply source R
 SAP AG

Excluding Materials from MRP
Plant 1200
MRP indicator
= “blank“
Stor. Loc. 1
Replenishment
using MRP
MRP indicator
= “blank”
Stor. Loc. 2
Material K
MRP indicator = 1
Replenishment
using KANBAN
Stor. Loc. PL03
 SAP AG

General Procedure in KANBAN
11 Master Data
22 General Procedure
 SAP AG

Setting a Kanban to Empty
Production process
fu l l Replenishment
is triggered
empty automatically
• Order
Supply area Status to empty • Purch.
Purch. order...
source
Supply
Ext. procurement Stock transfer In-house prod.

R
 SAP AG

Setting Kanban to Full
Production process
l
Ful
Goods receipt
is posted
automatically
Supply Area Status to full
Full
Full Kanban
source
Supply
Ext. procurement Stock transfer In-house prod.

R
 SAP AG

KANBAN Board
Status change
Status to empty Status to full
Supply Area Container
Material
Container qty You can set me
to empty.
Supply area Line 3
R-1230 Bios
20 pc.
R-1240 Motherboard
20 pc.
You can set me
Supply area Line 4 to full.
R-1230 Bios
20 pc.
Various views and selection options allow optimal

monitoring and evaluation R
 SAP AG

KANBAN: Summary
In this topic, you have become familiar with KANBAN as an

alternative for controlling material flow in the production
process.
 SAP AG

MM Scheduling Agreement Processing: Unit
Objectives
to:
Outline the structure of a scheduling agreement, and

Create and set the basic controls for forecast
delivery schedules and JIT delivery schedules.
Describe the sales process using cumulative
quantities.
 SAP AG

MM Scheduling Agreement Processing:
Business Scenario
Components are to be procured using
scheduling agreements.
 SAP AG

MM Scheduling Agreement - General
Scheduling
Scheduling Agreement
Agreement
1.4.1998
1.6.2004
 SAP AG

MM Scheduling Agreement - Main Points
Administrating different types of delivery schedule

(forecast delivery schedule (FDS) and JIT delivery
Sched.
schedule (JDS))
Sched. Agt.
Agt.
Dispatching the delivery schedules per EDI
1.4.1998
Transmission according to delivery schedule
1.6.2004
creation profile
Updating delivery schedule histories
Management of cumulative quantities
 SAP AG

MM Scheduling Agreement - Initial Screen
Control data
Vendor
Contract type: LPA sched. agt with delivery sched.
Sched. Contract date

Sched. Agt.
Agt.
Contract (external document no.)
1.4.1998
1.6.2004 Organizational levels
Purchasing organization Mandatory
Purchasing group levels
 SAP AG

MM Scheduling Agreement - Structure
Header
Header Vendor
Vendor :: 5401
5401
Item
Item Material:
Material: 4712
4712
Schedule 05.10.98 75 05.10.98 30

lines 12.10.98 90 06.10.98 20
... 07.10.98 25
12.10.98 ...
....
Delivery
Delivery schedules
schedules FDS 5 JDS 25 History
formation
Schedule 05.10.98 75 05.10.98 30

lines 12.10.98 90 06.10.98 20
... 07.10.98 25
12.10.98 ...
....
R
 SAP AG
There is an option for creating more than one scheduling agreement item under a single header.
However, SAP recommends that you use only one item per header. This is the more common procedure
and also allows for a better overview, system performance and error processing.
Each delivery schedule contains schedule lines, which are historized together with the delivery
schedules.

Control Data for Forecast Delivery Schedules
Scheduling Agreement
Header Customizing:
Sched. agt. indicator
Doc. type LPA Del. sched. documentation
Vendor 1000 Vendor master record
Item 10:
Material master record:
JIT indicator
Material 2000
1
JIT indicator 1
Creation profile 0001 Customizing (plant-referenced):

- Creation rhythm of del. sched.
- Aggregation of schedule lines
R
 SAP AG

Procurement Process with Scheduling
Agreements
1
% Net requirements calculation
MRP
MRP % Scheduling
% Update of the schedule lines
% Line aggregation as per del. schedule creation profile

Delivery
Delivery schedule
schedule creation
creation % Deadline/alteration-oriented delivery schedule creation
Delivery
Delivery schedule
schedule % Message output
transmission
transmission
 SAP AG

MRP
Order Book
St
Orderbuch
t
Planning
Entry relevant to
Basic scheduling
planning
agreement line
Automatic sched. agr.
formation
line formation
Net reqmts. calculation
Scheduling
Delivery Update of scheduling

schedule agreement schedule lines
Identification of
scheduling agreement as
altered
R
 SAP AG

Scheduling Agreement Releases
Forecast EDI, ...

delivery
schedule
.0D
>3
Scheduling Schedule
agreement line Vendor
Vendor
>4
.0A
EDI, ...
JIT
delivery
schedule
 SAP AG

Release Creation
Generating scheduling agreement releases
Selection by plant, vendor, material, scheduling E with next creation date

agreement, scheduling agreement item
Nächstes Abrufdatum
Release type FDS or JDS
<= aktuelles Datum ? !
Creation strategy
E only altered sched. agts
Sched. line situation altered
manually or automatically since
Creating a new delivery Updating the last delivery last del. sched. outputting? !
schedule schedule
Last delivery schedule Last delivery schedule

already outputted? ! not yet outputted? !
Sched. agt Aggregation Delivery
schedule as per schedule
lines creation lines R
profile
 SAP AG
A delivery schedule creation run can generate either a forecast or a JIT delivery schedule.
The creation strategies With next creation date and Altered scheduling agreements only are mutually
supplementary (AND operation).

Aggregation with the Release Creation Profile
Customizing:
Aggregation horizons in working days
Scheduling
agreement Forecast delivery schedule: JIT delivery schedule:
No aggregation 0- 2 No aggregation 0-2

Item 10: Daily aggregation 3 - 10 Daily aggregation 3 - 5
Creation profile 0001 Weekly aggregation 11 - 20
Quantity
JIT
delivery
schedule
Forecast
delivery
schedule
Schedule
line
R
Zeit
today Mo Tu We Th Fr Sa Su Mo Tu We Th Fr Sa Su Mo Tu We Th Fr Sa Su Mo Tu We Th Fr Sa Su
Week n Week n+1 Week n+2 Week n+3
 SAP AG
In the release creation profile, you can determine the creation rhythm, the aggregation of the schedule
line quantity and the release horizon.
Subdivision of the FDS and JDS horizons into different aggregation horizons by specifying the horizon
end (in working days):
No aggregation: the schedule lines are transferred unchanged from MRP.
Day-referenced aggregation: for day-referenced schedule lines in the short-term horizon range for
JDS or FDS
Aggregation by planning calendar: expedient when you have to allow for particular delivery days
Week-referenced aggregation: to-the-week schedule lines in the medium-term horizon range as a
forecast in the FDS
Month-referenced aggregation: accurate-to-the-month schedule lines in the long-term horizon range
as forecast in the FDS
The furthest aggregation horizon determines the release horizon.
The schedule line periods are always concluded completely before a new schedule line period begins.
For example, at the transition from week-referenced to month-referenced aggregation, the schedule lines
for the week in which the first of the month falls are aggregated on a week-referenced basis.

Message Control
Message Control:
Customizing Application: EL
Msg. determination schema : RMBEL1
Document type: LPA
Condition 109 Condition111

Print operation 9 Print operation A
*) With regeneration of Message types for FDS: Message types for JDS:
print-dependent data LPH1 for main message *) LPJ1 for main message*)
LPH2 for additional message LPJ2 for additional message
Purchasing
Message records per message type:

Medium EDI: message record for each vendor/purchasing
organization/document type
Medium print: message record for each document type R
 SAP AG
Separate types of message for forecast delivery schedule and JIT delivery schedule
Identification of precisely one message type per print operation as relevant for update of print-dependent
data (including output date, output time) and resetting the alteration indicator in the scheduling
agreement item.
Additional messages for printing as a supplement to EDI transfer

Administration of Delivery Schedule
Generations
New delivery schedule replaces old delivery schedule

(FDS/FDS und JDS/JDS)
Any delivery schedule generations can be compared
FDS / FDS
JDS / JDS in a table and in a graphic
Example:
Example: FDS 1 FDS 2
Date Quantity CQ Date Quantity CQ

01.07. 1000 1000 01.07. 1500 1500
01.08. 2000 3000 01.08. 1000 2500
01.09. 1000 4000 01.09. 2000 4500
01.10. 1000 5000 01.10. 1000 5500
 SAP AG

Cumulative Quantitites - Definition
Monitoring sales/procurement transactions between

business partners
Customer Vendor
!!
??
 SAP AG

Cumulative Quantitites - Examples
Σ Σ Σ Examples:
Cumulative received quantity (CRQ)

Cumulative quantity of goods receipts for a scheduling
agreement item.
Σ Σ Σ .
Cumulative scheduled quantity (CSQ)
The cumulative scheduled quantity is the sum of the
cumulative goods receipt quantity and the cumulative
open line quantitiy up to the key date of the line concerned.
It is recorded as the current cumulative scheduled quantity
in the scheduling agreement item and in the delivery
schedule, in order to document the cumulative scheduled
quantity when the delivery schedule line is called off.
R
 SAP AG

Reconciliation of Cumulative Quantities
It is necessary to reconcile cumulative quantities

with the vendor
Customer Vendor when you start using R/3 MM scheduling agreements
if there are differences between your cumulative quantities
?? !! and the vendor‘s
at the turn of the year
Reconciliation is carried out against the

reconcilation date, and
agreed cumulative quantities
 SAP AG

Releases for the Supplier
Production line
Repetitive Mfg
Firm zone (production release)
Trade-
Trade-off zone (material release)
 SAP AG

Contract-Referenced Scheduling Agreement
Creating a scheduling agreement with reference to a contract
Scheduling agreement
55...40
Vendor A
Term begins: 01.01.1998
Term ends: 31.12.9999
Item 10
Plant 0001 Contract 46...100
Material X
Vendor A
Price: 10 DM/PC (Reference)
Term ends: 31.12.9999
Scheduling agreement Position 10
55...41 Material X
Vendor A
Price: 10 DM/PC
Term ends: 31.12.9999
Position 10
Plant 0002
Material X
Price: 10 DM/PC (Reference)
R
 SAP AG
Scenario:
The purchasing organization concludes long-term outline agreements (value or quantity contracts)
with the vendor for all materials to be procured. The prices and conditions are agreed, and will be
renegotiated and modified at need.
The plant itself agrees with a vendor, with reference to this contract, how its production operation is
to receive a long-term supply of particular materials. In this context, only questions of quantity flow
are significant.
When a contract-referenced scheduling agreement is created, a reference to the conditions (price,
surcharges/discounts) can be built up. Goods receipts under the scheduling agreement are then valued
using the conditions from the contract. More than one scheduling agreement item can be referenced to
one contract item.
Only the pricing of the scheduling agreement is referenced to the contract, meaning that as long as no
conditions have been updated in the scheduling agreement itself, the pricing is determined by the
contract.
The referenced contract or contract item is shown in the scheduling agreement under Header Statistics
General or Item Statistics General

MM Scheduling Agreement Processing:
Summary
The structure of a scheduling agreement, and how to

The basic elements of forecast and JIT delivery schedules,
and how to set the controls for them (delivery schedule
creation profile).
How sales processes are monitored using cumulative
quantities.
 SAP AG

Internet Scenarios: Unit Objectives

to:
Describe the basic technical requirements for
internet scenarios.
Describe the internet scenarios presented from the
following areas:
Materials Management
Sales and Distribution
Production Planning
 SAP AG

Internet Scenarios: Business Scenario
The following areas are optimized by

integrating Internet and Intranet:
Production Planning
 SAP AG

Internet Scenario: Materials Management
 SAP AG

Internet: Integration of R/3 with External Catalogs
Display and select

from external catalogs
INTERNET
Transfer
Product
Price
R/3 MM Quantity
Availability
External catalogs
(R/3 or not R/3)
Creation
R/3
R/3 MM
MM
Purchase requisition
Purchase order
Reservation
INTRANET
R
R/3 SD
 SAP AG

Data Transferred
URL of IAC
R/3 System Catalog
Description / Material number

Quantity / quantity unit
Price / price unit
Currency
Time till availability
Vendor
Material number of vendor
O.E.M.‘s part number
O.E.M.
R
 SAP AG

Scenario 1 for Procurement Using Catalogs:
Intranet - Entire Data Processing Inside the
Firewall Search in catalog
Internet
Catalog
DB
Application
LAN External
External
companies
companies
Firewall
Intranet User
Creating a reservation/
purchase requisition/
R
purchase order
 SAP AG
Release 4.0 has a new IAC: procurement using catalogs. This IAC provides a variety of scenarios.
The scenario depicted above is purely internal. No data processing takes place outside the firewall.
Reservations, purchase requisitions or purchase orders are created using an Internet browser.
The catalog search can be integrated into the process.

External Catalog Search in catalog External
Catalog
Internet
DB
Application
LAN External
External
companies
companies
Firewall
Internet User
purchase requisition/
R
purchase order
 SAP AG
In the scenario depicted above, it is only the catalog search which goes beyond the firewall. The
remaining data processing takes place inside the firewall.

R/3 Product Catalog Internet
DB External
SD-System
Application
LAN
R/3
Firewall
Internet User Search in the R/3 Product Catalog
Creating customer orders

pruchase requisition /
R
purchase order
 SAP AG
In this scenario, the vendor utilizes the R/3 system. If the vendor agrees, it is possible to send the
purchase order to the vendor over the Internet and to create the sales order directly in the vendor's
system.
The sales order number is transferred by the vendor's system and incorporated in the purchase order item
as the order confirmation number.

Internet Scenario: Sales and Distribution
 SAP AG

Extended Sales Scenario
Accessing the product catalog
Order entry
Variant configuration
Information Functions
Sales order
Status
Transport/shipping information
Details of links to forwarding agents on Web pages
(Federal Express, UPS)
 SAP AG
Product catalog
For product presentations within the context of scenarios like pricing, availability checks, purchase
ordering or order entry, two functions are particularly crucial: simple "browsing" and graphical display.
Both these functions are incorporated in the product catalog. This application offers a clear hierarchical
structure, an easy-to-handle search machine, and an option for integrated graphics and texts.
Variant configuration
Order entry for variant products offers consumers an option for using the World Wide Web to place
purchase orders for industrial products like furniture or computers which are manufactured in different
variants. The consumers specify the particular product configuration they want. Example: a customer
would like to order a computer. He/she can access the manufacturer‘s website and specify processor
type, memory size, screen dimensions, and so on. The application then executes a consistency check for
the desired configuration, creates an order (including a BOM), and posts the order directly to the
production system. This reduces the lead time and enables customers to be served more efficiently.

Order Entry over the Internet
 SAP AG

SAP’s Product Configurator
 SAP AG

Internet: Creating Sales Orders
 SAP AG

Internet Scenarios: Production Planning
 SAP AG

Production Planning (1): Internet KANBAN
Vendor is responsible for material availability

Vendor monitors KANBANs over the INTERNET
Vendors triggers replenishment over the INTERNET
R/3
 SAP AG
KANBAN
With KANBAN (Logistics), replenishment is triggered by the corresponding kanban being set to
empty. The kanbans and their status can be displayed in the Kanban board. In an Internet
environment, suppliers can access the customer's Kanban board, and view the kanbans for which they
are responsible. To refill an empty kanban container, the supplier creates a delivery in his own
system, and dispatches the material required. Both companies profit from this transparency. Just-in-
Time deliveries are optimized. The business processes involved go beyond the boundaries of the
individual company. In this case, responsibility for delivering the goods concerned directly to the
production line is transferred from the O.E.M. to the supplier.

Production Planning (2)
Availability Queries for Sales

Partners and Customers
Selection of products which are important
for the sales partner concerned
Detailed availability information (ATP)
Overview of the current prices
 SAP AG
Availability queries
With the Available to Promise component (Logistics), the customer links up with a system and enters
material, plant, quantity and desired delivery date there. The result is ‘Yes' or 'No'; with ‘Yes ‘a
delivery date is quoted. Advantages: Each customer can fetch the information he/she needs on-line,
thus reducing the number of telephone calls involved. The accelerated information flow renders
business life more dynamic. Target group: buyers at other companies or Internet users.

Internet Scenarios: Summary
In this topic, you have become familiar with ways

of optimizing the following areas using selected
Internet scenarios:
Production Planning
 SAP AG

What’s Next in Automotive?:
Unit Objectives
At the conclusion of this unit, you will have

an overview of planned automotive
developments, especially in the following
areas:
Sequenced JIT call
Bordero Procedure
Packaging Logistics
 SAP AG

Delivery Schedule Types for Scheduling
Ageements
MONTHLY QUANTITIES (Delivery schedule)
J F M A ... weekly
weeklyor
ormonthly
monthly
quantities
quantities
DAILY QUANTITIES (JIT delivery schedule)
01 02 03 04 05 06 07 08 09 ... daily
dailyquantities
quantities
SEQUENCED JIT CALL

per
pervehicle
vehicle
 SAP AG

Bordero: Definition
Fwdg Agent S
Transport 320
Supplier A Supplier A Supplier B

Customer X Customer Y Customer X
Shipment 4711 Shipment 4712 Shipment 1234
Delivery 0815 Delivery 0817 Delivery 1810
Delivery 0816 Delivery 0818 Delivery 1811
Customer X
Transport 747
 SAP AG
A ”bordero” is the quantity of goods on one mode of transport (truck, train, container...) and generally
contains delivery groups/deliveries from various suppliers to various customers.
Each participating partner has a specific view of the bordero. These views can be represented by the
partners' shipments (forwarding agent, supplier, customer).
The forwarding agent usually has the complete view, that is, the bordero is one shipment from the
forwarding agent. The other partners only see the delivery group concerning them.
The individual shipments are linked by the bordero number. This identification is set by the shipment
controller (in this case, the forwarding agent).
You must make sure that the individual objects (delivery, delivery group, shipment) have a clear and
exclusive link with the appropriate partner (Example: customer X and customer Y each have a delivery
with number 0815).
R/3 shows the above bordero as a stop-off shipment for customer X and an individual shipment for
customer Y.

Bordero: Definition
Delivery: quantity of goods shipped simultaneously

from one point of departure to one unloading point
Delivery group: group of deliveries for one goods
recipient (that is customer plant)
Bordero: quantity of all delivery groups on one mode
of transport
Shipment: quantity of all delivery groups in a bordero
that are relevant for a business partner
Bordero <=> Shipment
 SAP AG
VDA 4920 (S.11) and VDA 4921 (S.9): A delivery group is the quantity of goods that a dispatcher of
goods/supplier uses a forwarding agent to send to the customer/goods recipient. A single delivery group
/ loading / reference number is allocated for this.
VDA 4913 (S.11): A delivery group is a maximum of one truckload. There can be one or more delivery
groups per truckload. If there are several delivery groups in one truckload, a separate DLR number is
allocated to all the delivery notes for one unloading point, if there is a shipping order for each unloading
point. The DLR number consists of the delivery group as a prefix and a counter as a suffix (S.32).
VDA 4921 (S.20): The bordero is a grouping together of all the individual delivery groups collected by
one forwarding agent for one goods recipient.
VDA 4922 (S.3): The participants decide whether the form (shipping order, note) is created per
unloading point, per plant or per delivery group / loading / reference number.
With VDA 4922 (shipping order), then, it is possible to enter the unloading point at item level per
delivery note, rather than in the header. Prerequisite: unloading points must have the same address.
This is also confirmed in VDA 4912 (S.4): all items with the same unloading point number are
summarized on one sheet (several if required). There can be several different delivery note numbers on
one sheet. It is therefore one message (printout) for the whole delivery group.

Bordero: Aim of Process
Simplified goods receipt

Shipment cost settlement with forwarding agent
Monitoring of shipments
 SAP AG
Goods receipt should take place for the whole shipment, or for all packages (as default-setting) in the
shipment. Entering goods receipt in advance (transfer of property) is also recommended (though
difficult from an inventory management point of view).
In the main scenario, the forwarding agent procedure, shipment cost settlement takes place. An
extensive range of functions are provided for this in Release 4.5A.
An additional problem is the changing of objects. This applies both to the delivery (shipping
notification) and the shipment. The delivery is the planning element. The forwarding agent or carrier
normally sends a message via EDI if anything has changed (affects material requirements planning for
the goods recipient). The information can also simply be for monitoring purposes (shipment status).

Bordero: Information Flow
Supplier Shipping notification Customer
Forwarding rqmts Transport notification
Forwarding
Status notification Status notification
agent
 SAP AG
Processing with a forwarding agent (planning and execution) as described in norms VDA 4913 (S. 6)
and VDA 4920/21 ( both S. 5) is the classic scenario.
All essential communication takes place via EDI. The bill of lading (shipping order) in accordance with
VDA 4922 is an accompanying document. The most important printed function is the material tag that
identifies the packages, in accordance with VDA 4902. The goods receipt/issue slip is optional (for use
instead of a delivery note) and represents the ”print output” of the shipping notification.
If the forwarding agent changes a delivery group, the information must be passed back to the supplier.
No detailed procedure is given for this in the norms, although it is specifically stated that changes are
possible.
One main question is: Which information is passed on and when? That is, when are the EDI messages
transmitted to the participating partners? Possible time-spots are: creation, picking or goods issue of
delivery/delivery group, or planning or completion of shipment. Alternativ könnten Objekte selbst
erzeugt werden (Sammelgang für Lieferavise); in this case, messages only serve monitoring and
correction purposes. Dies hängt von der Abwicklungsform ab.

Bordero: Material Flow
Departure Goal
Departure Load trfr pt Load trfr pt
Departure Goal
Suppliers Forwarding agents Customers
 SAP AG

Packaging Logistics
Packaging
Packaging
material
material
logistics
logistics
Material
Material Packing
Packing
logistics
logistics
Package
Package
administration
administration R
 SAP AG

Packaging Materials Logistics
Procurement
Procurementof
of
packaging
packagingmaterials
materials
Inventory
Inventorymgt
mgtofof Shipping
Requirements
Requirementsplanning
planning Shipping
packaging materials
packaging materials packaging
for
forpackaging
packagingmaterials
materials packagingmaterials
materials
Reconciliation
Reconciliationof
of
packaging
packagingmaterials
materials
Material
Material Packing
Packing
Logistics
Logistics Package
Package R
administration
administration
 SAP AG

Package Administration (HUM)
Material Packaging
Packaging
Material Packing
Logistics mat.
mat. logistics
logistics Packing
Logistics
HU-
HU -based
HU-based
production
production
HU-
HU-based
HU-based HU HU-
HU-based
HU-based
goods HU
goodsreceipt
receipt administration
administration
shipping
shipping
HU-
HU -based
HU-based HU-
HU -based
quality HU-based
qualityassurance
assurance stockkeeping
stockkeeping
R
 SAP AG

Packing According to Packaging Instructions
Automatic packing according to packaging instructions =
Proposals for HUs (packages) created according to master data for
packaging instructions
User confirms or changes proposals for the HUs created
BMW
BMW
Munich
Munich Automatic
Input Automatic Output
Mat.
Mat.4711
4711 packing
200
packing
200pieces
pieces
BMW
BMW
Regensburg Automatic
Automatic
Regensburg Input Output
Mat.
Mat.4711
4711 packing
packing
100
100pieces
pieces
R
 SAP AG

Customer-Specific Packing in Production
Production order (no ref. To customer): Material 4711, 500 pieces
Packing order 1 Packing order 2 Packing order 3 Packing Packing order 5

Vo18 200 pc. Vo33 60 pc. Vo66 72 pc. order 4 Vo22 140 pc.
Vo17 28 pc.
BWM Audi BMW Make-to-stock

München Ingolstadt Regensburg production
R
 SAP AG

What’s New in Automotive? : Summary
You have gained an overview of planned

developments in the automotive area.
 SAP AG

Exercises
Note:
You may not be able to complete all the
exercises within the time allowed for the
course. The exercises are provided as
additional examples, which can be carried out
after the course if necessary. Participants can
also use them to consolidate their knowledge
after the course.
 SAP AG

Unit: IAU210 Introduction
You are familiar with how the automotive logistics chain is

represented in R/3, with and without the integration of an external
service agent.
You can outline the EDI procedure using the IDoc interface.
You can assign to business processes the message types supported in
Release 4.0B.
Starting from the OEM's MM scheduling agreement, forecast and JIT
delivery schedules are sent via EDI to suppliers. The suppliers deliver
against the JIT delivery schedules and bill the deliveries (internally). The
OEM carries out evaluated receipt setttlement and executes a payment
run, dispatching credit memo and payment advice notes.
1-1 In this unit, you dealt with the automotive logistics chain.
1-1-1 Which are the main parties involved in the value-added process?
__________________________________________________________
1-1-2 What are the main tasks of an external service agent?
__________________________________________________________
1-1-3 In the scenario "without ESA", which messages are dispatched per EDI
betweeen supplier and OEM.
What are the corresponding IDocs called?
Message IDoc _

Unit: SD Scheduling Agreement Processing
• You are able to describe the structure of a scheduling agreement and to

maintain scheduling agreements, forecast delivery schedules and JIT
delivery schedules.
• You know the options for control and comparison of forecast and
planning delivery schedules.
• You can maintain scheduling agreements with delivery orders.
• You know the basic differences between the two procedures.
The automotive OEM and its suppliers negotiate scheduling agreements
to represent a long-term customer-vendor relationship.
For planning purposes, the customer dispatches forecast delivery
schedules to the supplier.
The vendor receives the customer's JIT delivery schedules and delivery
orders to be delivered.
1-1 In this exercise, you create a scheduling agreement and set the controls for delivery
schedules.
1-1.1 For sales organization 0020, distribution channel direct sales and division High
Tech, create a scheduling agreement with delivery schedules for sold-to party
2002 and material AZ2-600. The scheduling agreement should refer to item 010
of the customer scheduling agreement 1-1.1-## .
Now save the scheduling agreement.
Scheduling agreement no: _
1-1.2 The system has automatically determined the customer material no, the shipping
point and the delivering plant. Where did it get the information?
Customer material number from:_____________________________
Shipping point from: ______________________________________

Delivering plant from:______________________________________

1-1.3 With SAPSOTA AG, it was agreed that forecast delivery schedules would
generally only be used for planning and JIT delivery schedules only for
shipping.
Set the controls for delivery schedules accordingly.
Create the first forecast delivery schedule for your scheduling agreement, for
today's date, with the following schedule lines:
Current month: 50
Current month + 1: 50
Create a JIT delivery schedule simultaneously, by distributing the schedule line

quantities according to the forecast delivery schedule as daily quantities over the
corresponding months.
Save the scheduling agreement and double-check that only the requirements from
the forecast delivery schedule have been passed on to requirements planning.
Scheduling agreement no.:______________________________________
Access the scheduling agreement again and display the comparison of forecast and
JIT delivery schedules, in a table and in a graphic.
1-2 Optional:
In this exercise, you create two scheduling agreements with delivery orders, and a
corresponding delivery order with two materials.
Tech, create a scheduling agreement with delivery order for sold-to party 2002
and material AZ2-600. The scheduling agreement should refer to item 010 of
customer scheduling agreement 1-2.1-##.
1-2.2 At the same time, create a scheduling agreement for material AZ2-730 (PO
number 1-2.2-##).

1-2.3 What planning type has the system automatically assigned?
Planning type:______________________________________
1-2.4 Create the first forecast delivery schedule for your scheduling agreement, for
Current month: 50
1-2.5 Now create one delivery order for the materials from the above scheduling
agreements. The customer wants 10 air conditioning units and 15 navigation
systems for one week from today, to be picked up between 10:00 and 12:00. The
customer's PO number is 1.2-##.
1-2.6 Display the total cumulative quantities and the quantities in transit for the
scheduling agreements from exercises 1-1.1 and 1-1.2.
Total cumulative qty:_____________and_____________________
Cumulative qty in transit____:_____________and_____________________

Unit: Shipping Activities
• You can explain and execute the basic steps in the shipping process:
• Shipping point determination
• Route determination
• Delivery creation
• Picking
• Posting goods issue
• Dispatching the shipping notification
You create deliveries for the SD scheduling agreement in accordance

with the (JIT) delivery schedule dates. You notify the goods recipient of
dates and quantities in a shipping notification.
1-1 List the basic steps in the shipping process.
_____________________________________________________________
_____________________________________________________________
1-2 Access the table for shipping point determination in Customizing.
1-2-1 On which criteria does the system base automatic shipping point determination?
_______________________________________________________

1-2-2 Describe where these criteria come from and to what extent they can be
changed in the scheduling agreement.
_______________________________________________________
_______________________________________________________
_______________________________________________________
_______________________________________________________
_______________________________________________________
_______________________________________________________
1-3 Optional:
Set automatic route determination.
1-3-1 Create a route for the delivery of air conditioning unit AZ2-600.
Route: GB-D##
Description: ## GB -> D
Shipping type: 04 (Ship)
1-3-2 Maintenance of the route determination table is based on zones. Since the route
determination in this exercise is to be relevant for customer 2002 as goods
recipient, you now go to the customer master to see which transportation zone
the customer belongs to (view “Control data”).
_______________________________________________________
1-3-3 Set route determination so that, under the express shipping condition ("as soon
as possible"), the system automatically determines the route you have just
defined.
For shipping point: 2000

To country: DE
Zone: determined in 1-3-3
Shipping condition: 01
Transportation group: 0001
Proposed route: GB-D##

1-3-4 You have maintained the route determination table firstly by entering a
shipping point. When you make this entry, the system automatically determines
the departure zone assigned to the shipping point in Customizing.
Which departure zone is assigned to shipping point 2000?
_______________________________________________________
1-3-5 Check your route determination settings by entering shipping condition 01 in

the scheduling agreement with delivery schedules (from the exercises in the
"SD Scheduling Agreement Processing" unit), and then execute route
determination.
1-4 Deliver the first JIT delivery schedule for the scheduling agreement with delivery
schedules from the exercises in the "SD Scheduling Agreement Processing" unit.
1-4-1 Create the delivery for the first JIT delivery schedule, starting from the
What are the picking status and the Warehouse Management activity status of
the delivery?
Save the delivery.
Look at the scheduling agreement document flow. What is the status of the
delivery?
1-4-2 Access the delivery in change mode and start the picking process from here
(using Lean Warehouse Management).
the delivery now?
delivery and the (WM) transfer order?
1-4-3 Post the goods issue for your delivery.
(WM) transfer order and the goods delivery?
Explain the status of the delivery.

Unit: Billing, Credit Memo Procedure
• You can carry out billing for the delivery schedules.

• You can make the basic Customizing settings for the billing process
demonstrated.
You bill the JIT delivery schedules that you delivered in the "Shipping
Activities" unit.
1-1 In this exercise, you carry out delivery-related billing for some of the JIT delivery
schedules that you delivered in the last unit.
1-1-1 Starting from the Shipping menu, create the billing document for one of your
JIT delivery schedules from the "Shipping Activities" unit.
No. of billing document: _______________________
1-1-2 Display the accounting document for your billing document.

Which document does your accounting document refer to?
_______________________________________________________
1-2 Optional:
Verify a few important Customizing settings for your billing operation.
1-2-1 Check which billing document types are assigned to your scheduling agreement
in Customizing.
__________________________________________________________
1-2-2 Is the scheduling agreement to be billed with reference to order or with

reference to delivery? Why?
____________________________________________________________
(C) SAP AG IAU210 10-10

1-2-3 Does the system carry out new pricing for your scheduling agreement when a
delivery is created? If so, why?
____________________________________________________________
1-3 Goods receipts were posted at SAPSOTA AG for the schedule lines you delivered.
SAPSOTA AG has agreed with its suppliers (1098 and 1099), that goods receipts are
to be settled using ERS (evaluated receipt settlement).
1-3-1 Where do you set the system to use ERS settlement with suppliers 1098 and
1099?
____________________________________________________________
1-3-2 In the examples, a goods receipt was settled for material AM2-730. From which
documents did the system take the relevant data for the goods receipt
settlement?
____________________________________________________________
1-3-3 Why is it advisable to work with the logistics invoice verification in an EDI
environment?
____________________________________________________________
(C) SAP AG IAU210 10-11

Unit: Scheduling Agreement Processing with an External
Service Agent
The customer sends forecast delivery schedules to the supplier, who in turn delivers to
the ESA (consignment fill-up).
The ESA receives JIT delivery schedules from the customer, makes the
deliveries, and informs the supplier accordingly.
The supplier posts the consignment withdrawal and bills it.
1-1 You use the external service agent ‘Speed and Partner‘ to ship to your customer
Sapsota AG.
1-1-1 Which document type must be used to create the scheduling agreement?
Document type:______________________________________________
1-1-2 Who receives Sapsota AG's
- forecast delivery schedules?:_________________________________

- JIT delivery schedules?:____________________________________
1-1-3 Who takes the following partner roles in the scheduling agreement?
- Sold-to party:__________________________________________
- Bill-to party: ___________________________________
- Payer:____________________________________________
- Ship-to party:_______________________________________
- Special stock partner:___________________________________
(C) SAP AG IAU210 10-12

1-2 In this exercise, you create a scheduling agreement, on which to base deliveries from
Leeds Manufacturing (creditor 1098) to SAPSOTA AG (debitor 2002), using the
external service agent Speed and Partner (ESA 1900).
1-2-1 For sales organization 0020, distribution channel direct sales and division
High Tech, create an ESA scheduling agreement for sold-to party 2002,
external service agent 1900 and material
AZ2-600. The scheduling agreement should refer to item 010 of customer
scheduling agreement 1-2-1-##.
Then save the scheduling agreement.
SchedAgt no.:_______________________________________________
1-2-2 Create the first forecast delivery schedule for your scheduling agreement, for
current month + 1: 50
1-3 Optional:
Now deliver the first JIT delivery schedule line of the scheduling agreement:
1-3-1 Starting from the scheduling agreement, create the delivery for the first JIT
delivery schedule line.
Save the delivery.
1-3-2 Starting from the delivery in change mode, pick the delivery.
Look at the scheduling agreement document flow.

(C) SAP AG IAU210 10-13

Unit: Production Processing
• You can use planning delivery schedules as an interface between Sales

and Distribution and Material Requirements Planning.
• You can explain make-to-stock repetitive manufacturing processes.
• You can use KANBAN as an alternative for controlling material flow.
• The requirements for the inbound forecast delivery schedules are

edited into planning delivery schedules and passed on to MRP.
• They are produced using repetitive manufacturing.
• Component stocks are replenished using KANBAN
1-1 From the inbound forecast delivery schedules, you are to generate planning delivery
schedules, with the following characteristics:
• automatic generation of planning delivery schedules

• schedule lines for 2 months from schedule date
• For the first month, monthly quantities should be converted into weekly
quantities.
1-1.1 Create an appropriate planning delivery schedule instruction.
Instruction: ‘GR##’
Delivery relevance: ‘‘
Basic date: ‘1’
Date type: ‘3’
Validity period: ‘2’
Adopt schedule lines: ‘‘
Automatic generation of planning DS: ‘X’
Description: ‘Profile group ##’
Splitting rule: ‘SD3’

Date type: ‘3’
Range of coverage: ‘1’
(C) SAP AG IAU210 10-14

1-1.2 Enter your planning delivery schedule instruction in the scheduling agreement
from the exercises for unit “SD scheduling agreement processing”.
1-1.3 Create a new forecast delivery schedule, with the following schedule lines:
P Period Order qty

M current month 50
M current month + 1 50
and save the scheduling agreement.
1-1.4 Access the scheduling agreement again, and check that the planning delivery
schedule has been generated according to your planning delivery schedule
instruction.
1-1.5 Which schedule lines were passed on to MRP;

the forecast delivery schedule lines?
the planning delivery schedule lines?
____________________________________________________________
(C) SAP AG IAU210 10-15

1-2 Optional:
The master data for the production of material AZ2-730 in plant 2000 have already been
prepared.
In the following exercise, you check that the entries for repetitive manufacturing are
correct.
1-2.1 Is the material authorized for repetitive manufacturing?
____________________________________________________________
1-2.2 According to the repetitive manufacturing profile, are production activities automatically
posted to the product cost collector at final backflush for this material?
____________________________________________________________
1-2.3 Check which production version can be used to produce the material in repetitive
manufacturing.
Which production lines can be used to repetitively manufacture the assembly?
____________________________________________________________
1-2.4 Look at the routing (group counter 1) for material AZ2-730 in plant 2000.
What is the production rate, that is, how many materials are produced per hour?
____________________________________________________________
1-2.5 Look at a run schedule header for material AZ2-730 in plant 2000. A run schedule header
represents the authorization for a material to be produced on a production line for a certain
amount of time. Check that the period of validity (run time) for the run schedule header has
been properly maintained:
Plant: 2000
Material: AZ2-730
Production version: 0001
Is the run schedule header for production version 0001 still valid? To find out, look at the
fields “Validity start” and “Validity end”.
____________________________________________________________
(C) SAP AG IAU210 10-16

1-3 Optional:
The component AZ2-731 (navigation system CPU) is to be staged using KANBAN.
1-3.1 Verify that material AZ2-731 in plant 2000 at storage location PL01 has been excluded
from MRP, meaning that the replenishment elements are generated not in the planning run,
but via KANBAN.
Is this material excluded from MRP at storage location PL01?
__________________________________________________________
1-3.2 Is the same material AZ2-731 also excluded from MRP at storage location 0001 in plant
2000?
____________________________________________________________
1-3.3 Look at the stock/requirements list for material

AZ2-731 in plant 2000.
How does the system display materials that are excluded from MRP at a storage location in
the stock/reqmts list?
____________________________________________________________
1-3.4 Supply area PVB_AZ_100 has been set up to stage materials at the production line.
Display the supply area PVB_AZ-100 in plant 2000 in Customizing for KANBAN.
To which storage location and person responsible is the supply area assigned?
____________________________________________________________
1-3.5 In plant 2000, component AZ2-731 in supply area PVB_AZ-100 is to be staged directly
at the production line.
Check the control cycle to see which replenishment strategy is used to stage material at the
production line.
____________________________________________________________
Look at the KANBAN board in the demand source view for supply area PVB_AZ_100 in plant 2000:
How many containers have been created in the R/3 system for the replenishment of material T-T7## , how many are
(C) SAP AG IAU210 10-17

full, empty, waiting?
____________________________________________________________
(C) SAP AG IAU210 10-18

Unit: MM Scheduling Agreement Processing
You are able to

• outline the structure of a scheduling agreement, and create scheduling
agreements and schedule lines.
• create and set the basic controls for forecast delivery schedules and
JIT delivery schedules.
• describe the sales process using cumulative quantities.
To make sure production is well supplied and to obtain good purchasing

conditions, components are to be procured using scheduling agreements,
which are valid over a long period of time.
1-1 In this exercise, you, as an employee in the strategic purchasing department

(purchasing group 0##, purchasing organization 1000) of SAPSOTA AG (plant
1000), create an (MM) scheduling agreement (order type LPA) for the procurement of
an air-conditioning unit (material AM2-600) from the supplier Leeds Manufacturing
(creditor no. 1098). You create forecast and JIT delivery schedules manually and
dispatch them. You expect Leeds Manufacturing to inform you of deliveries per
shipping notification (confirmation control key 0004).
1-1.1 With Leeds Manufacturing, you have agreed that monthly quantities will be given
in forecast delivery schedules with a horizon of up to 365 days.
In the JIT delivery schedules, the schedule lines are given
- within the next 7 days, not aggregated
- for days 8 – 365, as daily quantities
JIT delivery schedule lines that lie more than a year in the future are no longer to be
given.
Create the appropriate release creation profile GR##.
1-1.2 Is it possible to create JIT delivery schedules for material AM2-600? If so, why?
_______________________________________________________________
_______________________________________________________________
(C) SAP AG IAU210 10-19

_______________________________________________________________
1-1.3 Now create an appropriate scheduling agreement. It should be valid until the end of
the year 2004.
Don't forget to enter your release creation profile GR##!
You must maitain the following import data, since you are working with a cross-
country procurement process:
Import header
Mode of trnsprt-Border: 1 Sea
Office of entry: 1212 Hbg.-Köhlfleetdamm (ship)
Import item
Bus.transaction type: 11 final purchase/sale
1-1.4 Now create the following schedule lines for the air conditioning unit:
one line each week for the next 6 weeks

schedule line quantity of 5 pieces.
1-1.5 Now create a forecast delivery schedule and a JIT delivery schedule from your
schedule lines. Do this from the change mode of your scheduling agreement and
verify that the messages were created.
What is the status of the messages? Why?
_______________________________________________________________
_______________________________________________________________
_______________________________________________________________
1-1.6 Now dispatch firstly the forecast and then the JIT delivery schedules.
1-1.7 Verify the status, processing date, and transmission time-spot of your messages in
your scheduling agreement.
Status: __________________________/______________________________
Processing date and time: _______________/___________________
_______________/___________________
(C) SAP AG IAU210 10-20

(C) SAP AG IAU210 10-21
Solutions
 SAP AG

Unit: IAU210 Introduction
1-1 In this unit, you dealt with the automotive logistics chain.
1-1-4 Which are the main parties involved in the value-added process?
1) The tier X supplier.

2) The tier 1 supplier.
3) The vehicle manufacturer.
4) The dealer.
1-1-5 What are the main tasks of an external service agent?
1) To deliver to the customer from consignment stock.

2) In some cases, to carry out additional activities, such as set creation, packing
sets for assembly, assembling items, repackaging and so on.
1-1-6 In the scenario "without ESA", which messages are dispatched per EDI
betweeen supplier and OEM.
What are the corresponding IDocs called?
Message IDoc _
Forecast delivery schedule DELINS
JIT delivery schedule DELINS
Shipping notification DESADV / DESADT
Credit memo GSVERF
Payment advice note REMADV

Unit: SD Scheduling Agreement Processing
1-3 In this exercise, you create a scheduling agreement and set the controls for delivery
schedules.
Tech, create a scheduling agreement with delivery schedules for sold-to party
2002 and material AZ2-600. The scheduling agreement should refer to item 010
of the customer scheduling agreement 1-1.1-## .
Menu path:
Logistics Sales and distribution Sales Outline agreement Scheduling
agreement Create
Initial screen
Sched. Agreemt type: SSA SchedAg. w/ del.schd.
Sales organization: 0020 Sales org. UK
Distribution channel: 01 Direct sales
Division: 07 High Tech
General data
Sold-to party: 2002 SAPSOTA AG
PO number: 1-1.1-## (number of customer scheduling agreement)
Item overview
Material number: AZ2-600 Air conditioning
Ordering party
PO item: 010 (PO item from customer scheduling agreement)
1-3.2 The system has automatically determined the customer material no, the shipping
point and the delivering plant. Where did it get the information?
Customer material no: Customer material info record

Shipping point: Customizing, shipping point determination
Delivering plant: Customer material info record (details screen)

1-3.3 With SAPSOTA AG, it was agreed that forecast delivery schedules would
generally only be used for planning and JIT delivery schedules only for
shipping.
Set the controls for delivery schedules accordingly.
Access the scheduling agreement in change mode;

via the menu path Goto Header Sales, you branch to the maintenance screen
for sales data at header level;
set the indicator Planning to C.
Create the first forecast delivery schedule for your scheduling agreement, for
Current month: 50
Pushbutton "ForeDlvSched" from change mode of scheduling agreement; set

Dlv.schedule to 1 and Dlv.sched.date to today's date.
Create a JIT delivery schedule simultaneously, by distributing the schedule line

quantities according to the forecast delivery schedule as daily quantities over the
corresponding months.
Pushbutton "JIT dlv." From change mode of scheduling agreement; set

Save the scheduling agreement and double-check that only the requirements from
the forecast delivery schedule have been passed on to requirements planning.
Menu path:
Logistics Materials management Inventory management Environment
Stock Stock. / reqmts list
Material: AZ2-600
Plant: 2000
Access the scheduling agreement again and display the comparison of forecast and
JIT delivery schedules, in a table and in a graphic.
Access the scheduling agreement;

Pushbutton “ForeDlvSched” or “JIT dlv.”
Pushbutton “Analys.”

Select forecast and JIT delivery schedule;
Pushbutton “Compare” or menu path: Goto Graphics
1-4 Optional:
In this exercise, you create two scheduling agreements with delivery orders, and a
corresponding delivery order with two materials.
Tech, create a scheduling agreement with delivery order for sold-to party 2002
and material AZ2-600. The scheduling agreement should refer to item 010 of
customer scheduling agreement 1-2.1-##.
Menu path:
Logistics Sales and distribution Sales Outline agreement Scheduling
agreement Create
Initial screen
Sched. agreemt type: LZM Scheduling agreement with delivery order
Sales organization: 0020 Sales organization UK
General data
Item overview
Ordering party
PO item: 010 (PO item of customer scheduling agreement)
1-4.2 At the same time, create a scheduling agreement for material AZ2-730 (PO
number 1-2.2-##).
1-4.3 What planning type has the system automatically assigned?

select the menu path: Goto Header Sales to branch to the sales data at header
level;
the indicator Planning is set to E
1-4.4 Create the first forecast delivery schedule for your scheduling agreement, for
Current month: 50

Pushbutton "ForeDlvSched" from change mode of scheduling agreement; set
1-4.5 Now create one delivery order for the materials from the above scheduling
agreements. The customer wants 10 air conditioning units and 15 navigation
systems for one week from today, to be picked up between 10:00 and 12:00. The
customer's PO number is 1.2-##.
Menu path:
Logistcs Sales and distribution Sales Order Create
Initial screen
Order type: TAM Delivery order
Dialog box
Scheduling agreement: from exercise 1-2.1
Pick up date: one week from today
Time from: 10:00
to: 12:00
General data
Overview screen
Order quantity: 10
Menu path: Sales document Create with reference to scheduling agrmt
Dialog box
Scheduling agreement: from exercise 1-2.2
Overview screen
Order quantity: 15
1-4.6 Display the total cumulative quantities and the quantities in transit for the
scheduling agreements from exercises 1-1.1 and 1-1.2.
Display the scheduling agreements;

Choose the pushbutton "ForeDlvSched"
Total cml qty: 10 and 15
Cml qty in trns: 10 and 15

Unit: Shipping Activities
1-3 List the basic steps in the shipping process.
1) Creating the delivery

2) Picking
3) Packing (optional)
4) Transport (optional)
5) Goods issue
1-4 Access the table for shipping point determination in Customizing.

In IMG: Sales and Distribution → Shipping → Basic Shipping Functions → Shipping
Point Determination → Assign shipping points
1-4-4 On which criteria does the system base automatic shipping point determination?
Shipping condition
Loading group
Plant
1-4-5 Describe where these criteria come from and to what extent they can be
changed in the scheduling agreement.
Shipping condition: comes from the master record for the

sold-to party and can be changed
in the scheduling agreement,
(Goto→→ Header→ → Shipping)
Loading group: comes from the material master and
cannot be changed in the order (is not
displayed in the scheduling agreement;
display by selecting the item, then
Environment → Display material,
View "Sales: general/plant"
Plant: comes from customer material info,
master record for goods recipient or
material master (the system accesses the
master records in this order), and
can be changed in the order
(for example, in the shipping view of the item)

1-5 Optional:
Set automatic route determination.
1-5-1 Create a route for the delivery of air conditioning unit AZ2-600.
In IMG: Sales and Distribution → Basic Functions → Routes → Define

routes → Define routes and stages
Choose the pushbutton "New entries"
Route: GB-D##
Description: ## GB -> D
Shipping type: 04 (Ship)
Save the route.
1-5-2 Maintenance of the route determination table is based on zones. Since the route
determination in this exercise is to be relevant for customer 2002 as goods
recipient, you now go to the customer master to see which transportation zone
the customer belongs to (view “Control data”).
Logistics → Sales and distribution → Master data → Business partners →

Sold-to party/Ship-to party → Change → Change/Change centrally
Customer: 2002
Select the view "Control data"
Transport zone: D000020000

1-5-3 Set route determination so that, under the express shipping condition ("as soon
as possible"), the system automatically determines the route you have just
defined.
In IMG: Sales and Distribution → Basic Functions → Routes → Route

Determination → Define route determination in sales doc. (proposed routes)
Routes → Route determination
For shipping point: 2000

To country: DE
Zone: for 2-1-1, determines (D000020000)
Shipping condition: 01
Transportation group: 0001
Proposed route: GB-D##
Save your data.

1-5-4 You have maintained the route determination table firstly by entering a
shipping point. When you make this entry, the system automatically determines
the departure zone assigned to the shipping point in Customizing.
Which departure zone is assigned to shipping point 2000?
In IMG: Sales and Distribution → Basic Functions → Routes → Route

Determination → Define route determination in sales doc. (proposed routes)
Influencing factors → Departure cntr/zone

Shipping point 2000: Ctry GB, Depart zone 0000001000
or:
In IMG: Enterprise structure → Maintain structure → Definition → Sales

and Distribution → Define, copy, delete, check shipping point
Choose the activity "Define shipping point".
Go to the details screen for shipping point 2000.
Departure zone: 0000001000
1-5-5 Check your route determination settings by entering shipping condition 01 in

the scheduling agreement with delivery schedules (from the exercises in the
"SD Scheduling Agreement Processing" unit), and then execute route
determination.

Goto→ Header→ Shipping, enter shipping condition 01;
Choose the pushbutton: "Redetermine"
(C) SAP AG IAU210 11-10

1-6 Deliver the first JIT delivery schedule for the scheduling agreement with delivery
schedules from the exercises in the "SD Scheduling Agreement Processing" unit.
1-6-1 Create the delivery for the first JIT delivery schedule, starting from the
the delivery?
Save the delivery.
delivery?

Sales document→ → Deliver;
if necessary, enter the requested delivery date to select the delivery;
select item;
Item→→ Item details;
Pick status: A not yet picked
WM activ status.: A WM trsfr order reqd
Save the delivery
Display the scheduling agreement;

Environment→ → Display document flow;
Overall processing status of delivery: Open
1-6-2 Access the delivery in change mode and start the picking process from here
(using Lean Warehouse Management).
the delivery now?
delivery and the (WM) transfer order?
Access the delivery in change mode;

Logistics → Sales and distribution → Shipping
Delivery→→ Save and subseq.func. → Transfer order;
Warehouse number: 020;
Plant: 2000;
Choose Enter to save the transfer order

Select the item;
(C) SAP AG IAU210 11-11

Item→
→ Item details;
Picking status: C fully picked
WM activ. status.: C trsf ord confirmed

Overall processing status of delivery: Being processed
Overall processing status of transfer order: Completed
(WM) transfer order and the goods delivery?
Logistics→→ Sales and distribution → Shipping→

→ Delivery → Change
delivery;
Enter the delivery and choose the pushbutton "Post goods issue".

Overall processing status of delivery: Being processed
Overall processing status of transfer order: Completed
Overall processing status of goods issue delivery: Completed
The delivery is "being processed", since no subsequent document (billing

document) has yet been created.
(C) SAP AG IAU210 11-12

Unit: Billing, Credit Memo Procedure
1-1 In this exercise, you carry out delivery-related billing for some of the JIT delivery
schedules that you delivered in the last unit.
1-3-4 Starting from the Shipping menu, create the billing document for one of your
JIT delivery schedules from the "Shipping Activities" unit.
Menu path: Logistics → Sales and distribution → Shipping → Subsequent

functions
→ Create billing document
Document: Delivery number (from your notes for the last unit exercises,
or from the document flow of your
scheduling agreement)
No. of billing document: _______________________
(C) SAP AG IAU210 11-13

1-3-5 Display the accounting document for your billing document.
Which document does your accounting document refer to?
Menu path: Logistics → Sales and distribution → Billing→ Billing document

→ Display
Billing document: from exercise 1-1-1
Menu path: Overview → Accounting
Double-click on "Accounting document"
Field: Reference
The accounting document refers to the customer's PO number (customer's

scheduling agreement number).
1-4 Optional:
Verify a few important Customizing settings for your billing operation.
1-4-1 Check which billing document types are assigned to your scheduling agreement
in Customizing.
Customizing path:
Sales and Distribution → Sales → Sales documents→ Sales Document
Header
→ Define sales document types;
Access the Details display of sales document type "LZ";
Field: Dlv-rel.billing type: "F2"
Field: Order-rel.bill.type: "___"
1-4-2 Is the scheduling agreement to be billed with reference to order or with

reference to delivery? Why?
Sales and Distribution → Sales → Sales documents→ Sales Document Item

→ Define item categories;
Access the Details display of item category "LZN";
Field: Dlv-rel.billing type
Relev. for billing: "A" relevant for delivery-related billing documents
(C) SAP AG IAU210 11-14

1-4-3 Does the system carry out new pricing for your scheduling agreement when a
delivery is created? If so, why?
Sales and Distribution → Billing → Billing documents→ Maintain copying

control for billing documents;
select Copying Control: Delivery Note to Billing Document.;
Access the item display for copying control from LF to F2;
Access the Details display of item category "LZN";
Field: Pricing type: "P" Carry out new pricing
A new pricing is carried out when a delivery is created.
1-5 Goods receipts were posted at SAPSOTA AG for the schedule lines you delivered.
SAPSOTA AG has agreed with its suppliers (1098 and 1099), that goods receipts are
to be settled using ERS (evaluated receipt settlement).
1-5-1 Where do you set the system to use ERS settlement with suppliers 1098 and
1099?
Logistics → Materials management → Purchasing → Master data → Vendor

→ Purchasing → Display (current);
Select the field "Purchasing data";
Field 'AutoEvalGRSetmt Del.'
1-5-2 In the examples, a goods receipt was settled for material AM2-730. From which
documents did the system take the relevant data for the goods receipt
settlement?
The quantity to be settled, from the goods receipt document.

The conditions, from the scheduling agreement.
1-5-3 Why is it advisable to work with the logistics invoice verification in an EDI
environment?
In contrast to a standard invoice verification, the logistics invoice

verification is linked to message determination. It is therefore possible to
dispatch the credit memo to the supplier per EDI.
(C) SAP AG IAU210 11-15

(C) SAP AG IAU210 11-16
Unit: Scheduling Agreement Processing with an External
Service Agent
1-1 You use the external service agent ‘Speed and Partner‘ to ship to your customer
Sapsota AG.
1-3-4 Which document type must be used to create the scheduling agreement?
Document type: SAEX
1-3-5 Who receives Sapsota AG's
- forecast delivery schedules?: Leeds Manufacturing
- JIT delivery schedules?: Speed and Partner
1-3-6 Who takes the following partner roles in the scheduling agreement?
- Sold-to party: SAPSOTA AG

- Bill-to party: SAPSOTA AG
- Payer: SAPSOTA AG
- Ship-to party: Speed and Partner
- Special stock partner: Speed and Partner
1-4 In this exercise, you create a scheduling agreement, on which to base deliveries from
Leeds Manufacturing (creditor 1098) to SAPSOTA AG (debitor 2002), using the
external service agent Speed and Partner (ESA 1900).
1-4-1 For sales organization 0020, distribution channel direct sales and division
High Tech, create an ESA scheduling agreement for sold-to party 2002,
external service agent 1900 and material
AZ2-600. The scheduling agreement should refer to item 010 of customer
scheduling agreement 1-2-1-##.
Then save the scheduling agreement.
(C) SAP AG IAU210 11-17

Menu path:
Logistics Sales and distribution Sales Outline agreement
Scheduling agreement Create
Initial screen
Sched. agreemt type: SAEX Sched.Agreement ExAg
General data
Ship-to party: 1900 Speed and Partner
PO number: 1-1-2-## (number of customer scheduling
agreement)
Item overview
Ordering party
POitem: 010 (purchase order item from customer
scheduling agreement)
Menu path:
Goto Header Partners
Special stock partner (Partner function SB): 1900 Speed and Partner
1-4-2 Create the first forecast delivery schedule for your scheduling agreement, for
Pushbutton "ForeDlvSched"from the change mode of the scheduling

agreement; set Dlv. schedule to 1 and Dlv. Sched. date to today's date.
1-5 Optional:
Now deliver the first JIT delivery schedule line of the scheduling agreement:
1-5-1 Starting from the scheduling agreement, create the delivery for the first JIT
delivery schedule line.
Save the delivery.
(C) SAP AG IAU210 11-18
Sales document→ → Deliver;
if necessary, enter the planned GI date in the selection criteria;
save the delivery.
1-5-2 Starting from the delivery in change mode, pick the delivery.

Logistics → Sales and distribution → Shipping
Delivery→→ Save and subseq.func. → Transfer order;
Warehouse no.: 020;
Plant: 2000;
Choose Enter to save the transfer order.
Look at the scheduling agreement document flow.

Logistics→→ Sales and distribution → Shipping→

→ Delivery → Change
delivery;
Enter the delivery and choose the pushbutton "Post goods issue".

The delivery is "being processed", since no subsequent document (billing

document) has yet been created.
(C) SAP AG IAU210 11-19

Unit: Production Processing
1-4 From the inbound forecast delivery schedules, you are to generate planning delivery
schedules, with the following characteristics:
• automatic generation of planning delivery schedules

• schedule lines for 2 months from schedule date
• For the first month, monthly quantities should be converted into weekly
quantities.
1-4.1 Create an appropriate planning delivery schedule instruction.
Customizing path: Sales and Distribution Sales Sales Documents

Scheduling Agreements With Delivery Schedules
Maintain planning delivery schedule
instructions/splitting rules
Pushbutton: ‘Maintain planning delivery schedule instructions'

Instruction: ‘GR##’
Delivery relevance: ‘‘
Basic date: ‘1’
Date type: ‘3’
Validity period: ‘2’
Adopt schedule lines: ‘‘
Automatic generation of planning DS: ‘X’
Description: ‘Profile group ##’
Pushbutton: '-->Assign delivery schedule splitting rules'

Date type: ‘3’
Range of coverage: ‘1’
1-4.2 Enter your planning delivery schedule instruction in the scheduling agreement
from the exercises for unit “SD scheduling agreement processing”.
Select the item in the maintenance screen for the scheduling agreement.
Menu path: Goto Item More Delivery schedule control
PlanDSinstruction.: ‘GR##’
(C) SAP AG IAU210 11-20

(C) SAP AG IAU210 11-21
1-4.3 Create a new forecast delivery schedule, with the following schedule lines:
P Period Order qty

M current month 50
and save the scheduling agreement
See unit: SD Scheduling Agreement Processing
1-4.4 Access the scheduling agreement again, and check that the planning delivery
schedule has been generated according to your planning delivery schedule
instruction.
Display the scheduling agreement; pushbutton: “Planning delivery schedule”
1-4.5 Which schedule lines were passed on to MRP;

the forecast delivery schedule lines?
the planning delivery schedule lines?
The planning delivery schedule lines were passed on to MRP.
(C) SAP AG IAU210 11-22

1-5 Optional:
The master data for the production of material AZ2-730 in plant 2000 have already been
prepared.
In the following exercise, you check that the entries for repetitive manufacturing are
correct.
1-5.1 Is the material authorized for repetitive manufacturing?
Menu path:
Logistics Production Master data Material master
Material Display Display current
Material: AZ2-730
View: MRP 4
Plant: 2000
The material is authorized for repetitive manufacturing with the indicator "Repetitive
manufacturing" in the material master.
1-5.2 According to the repetitive manufacturing profile, are production activities automatically
posted to the product cost collector at final backflush for this material?
Customizing path:
Production Repetitive Manufacturing Basic Settings Specify control data for
repetitive manufacturing profiles,
Display the details view of production version 0001
No, the "Activities" indicator is set to "1" : No activity posting
1-5.3 Check which production version can be used to produce the material in repetitive
manufacturing.
Material: AZ2-730
View: MRP 4
Plant: 2000
Pushbutton: Versions
Go through the different versions, selecting each one and choosing "Details".
Which production lines can be used to repetitively manufacture the assembly?
According to the production version, the material can be produced on production lines AZ-
100 and
AZ-200.
(C) SAP AG IAU210 11-23

1-5.4 Look at the routing (group counter 1) for material AZ2-730 in plant 2000.
What is the production rate, that is, how many materials are produced per hour?
Menu path:
Logistics Production Master data Routings
Routings Rate routings Display
Material: AZ2-730
Plant: 2000
Group counter. 1
In columns “Basic quantity”, “Requirements” and “Unit", you see that there is a
production rate of 60 pieces per hour.
1-5.5 Look at a run schedule header for material AZ2-730 in plant 2000. A run schedule header
represents the authorization for a material to be produced on a production line for a certain
amount of time. Check that the period of validity (run time) for the run schedule header has
been properly maintained:
Plant: 2000
Material: AZ2-730
Is the run schedule header for production version 0001 still valid? To find out, look at the
fields “Validity start” and “Validity end”.
Menu path:
Logistics Production Repetitive manufacturing
Master data RS header Display
Plant: 2000
Material: AZ2-730
Today's date lies between “Validity start” and “Validity end”.
(C) SAP AG IAU210 11-24

1-6 Optional:
The component AZ2-731 (navigation system CPU) is to be staged using KANBAN.
1-6.1 Verify that material AZ2-731 in plant 2000 at storage location PL01 has been excluded
from MRP, meaning that the replenishment elements are generated not in the planning run,
but via KANBAN.
Is this material excluded from MRP at storage location PL01?
Menu path:
Logistics Production Master data Material master
Material: AZ2-731
View MRP 4
Plant: 2000
Storage location: PL01
The MRP indicator is set to “1", so storage location PL01 is excluded from MRP.
1-6.2 Is the same material AZ2-731 also excluded from MRP at storage location 0001 in plant
2000?
No, the MRP indicator is set to “ “.
1-6.3 Look at the stock/requirements list for material

AZ2-731 in plant 2000.
How does the system display materials that are excluded from MRP at a storage location in
the stock/reqmts list?
Menu path:
Logistics Production MRP
Evaluations Stock/reqmts list
“PL01 StLoc:not plnnd” is displayed in the MRP element data column in the row for the
storage location to be excluded.
(C) SAP AG IAU210 11-25

1-6.4 Supply area PVB_AZ_100 has been set up to stage materials at the production line.
Display the supply area PVB_AZ-100 in plant 2000 in Customizing for KANBAN.
To which storage location and person responsible is the supply area assigned?
Customizing path: Production Kanban

Define supply areas
Storage location: PL01 Supply area. Line az-100; Person responsible: 001 MEIER
1-6.5 In plant 2000, component AZ2-731 in supply area PVB_AZ-100 is to be staged directly
at the production line.
Check the control cycle to see which replenishment strategy is used to stage material at the
production line.
Menu path:
Logistics Production KANBAN
Control cycle Display
Material: AZ2-731
Plant: 2000
Supply area: PVB_AZ-100
Replenishment via stock transfer with reservation from storage location 0001.
1-6.6 Look at the KANBAN board in the demand source view for supply area PVB_AZ_100
in plant 2000:
How many containers have been created in the R/3 system for the replenishment of
material T-T7## , how many are full, empty, waiting?
Menu path:
Logistics Production Kanban
Control Kanban board Overv. Demand source
In the area selection, select “Supply area”and enter the above supply area. Choose
“Enter”. The system displays the kanban board.
3 containers have been created, the red ones are empty, the green ones full, the other one is
waiting.
(C) SAP AG IAU210 11-26

Unit: MM Scheduling Agreement Processing
1-2 In this exercise, you, as an employee in the strategic purchasing department

(purchasing group 0##, purchasing organization 1000) of SAPSOTA AG (plant
1000), create an (MM) scheduling agreement (order type LPA) for the procurement of
an air-conditioning unit (material AM2-600) from the supplier Leeds Manufacturing
(creditor no. 1098). You create forecast and JIT delivery schedules manually and
dispatch them. You expect Leeds Manufacturing to inform you of deliveries per
shipping notification (confirmation control key 0004).
1-2.1 With Leeds Manufacturing, you have agreed that monthly quantities will be given
in forecast delivery schedules with a horizon of up to 365 days.
In the JIT delivery schedules, the schedule lines are given
- within the next 7 days, not aggregated
- for days 8 – 365, as daily quantities
JIT delivery schedule lines that lie more than a year in the future are no longer to be
given.
Create the appropriate release creation profile GR##.
Customizing path: Materials Management Purchasing Scheduling

Agreement Maintain rel. creation profile for sched. agt
with rel docu.
Pushbutton: New entries

Plant: 1000
Creation profile (text): GR## creation profile GR##
In the “Forecast delivery schedule” group of fields in the row “Monthly

aggregation”, enter 365.
In the “JIT delivery schedule” group of fields in the row “No aggregation”,
enter 7.
In the “JIT delivery schedule” group of fields in the row “Daily aggregation”,
enter 365.
(C) SAP AG IAU210 11-27

1-2.2 Is it possible to create JIT delivery schedules for material AM2-600? If so, why?
Menu path: Logistics Materials management Material master;

Material: AM2-600
View: Purchasing
Plant: 1000
The field “JIT sched. indicator” is set to “1”, so JIT delivery schedules for the air-
conditioning unit can be created.
1-2.3 Now create an appropriate scheduling agreement. It should be valid until the end of
the year 2004.
Don't forget to enter your release creation profile GR##!
Menu path: Logistics Materials management Purchasing;

Outline agreement Scheduling agreement Create
Vendor known
Initial screen
Vendor: 1098
Agreement type: LPA
Purch.organization: 1000
Purchasing group 0##
Plant: 1000 (proposed data for the item)
Storage loc.: 0001 (proposed data for the item)
Header data
Validity end: 31.12.2004
Item overview (row for item 010)
Material: AM2-600
Target qty: 10000
Net price: 390,--
Import header
Mode of trnsprt-Border: 1 Sea
Office of entry: 1212 Hbg.-Köhlfleetdamm (ship)
Item details
Tax code: VN
ConfCtrlK: 0004 Shipping notification
IR: X (check)
GR-basedIV: X (check)
ERS: X (check)
Import item
Bus.transaction type: 11 final purchase/sale
(C) SAP AG IAU210 11-28

Menu path: Item More functions Additional data;
In the section “Output control”, enter the creation profile“GR##”.
1-2.4 Now create the following schedule lines for the air conditioning unit:
one line each week for the next 6 weeks

schedule line quantity of 5 pieces.

Outline agreement Scheduling agreement
Delivery schedule
Maintain;
Select item 10;
Menu path: Item Delivery schedule;
Create 6 rows with

Column ‘C’: D Day format
Column ‘Delivery date’: Monday of one of the next 6 weeks
Column ‘Scheduled quantity’:5
1-2.5 Now create a forecast delivery schedule and a JIT delivery schedule from your
schedule lines. Do this from the change mode of your scheduling agreement and
verify that the messages were created.
What is the status of the messages? Why?

Delivery schedule
Maintain;
Select item 10;
Menu path: Edit Generate forc. sched. or Generate JIT sched.;
Menu path: Header Messages;

The messsage “LPH1” was created for the forecast delivery schedule, and “LPJ1”
for the JIT delivery schedule.
Both message have a status of “not processed” (yellow light), since the system is
only to dispatch them when specifically requested to do so.
Select a message;
Menu path: Further data;
Dispatch time (from message determination): 3 Explicit request
(C) SAP AG IAU210 11-29

1-2.6 Now dispatch firstly the forecast and then the JIT delivery schedules.

Messages
Print/transmit;
Purchasing doc.: Number of your scheduling agreement

Message application: EL
Message type: LPH1 / LPJ1
Select the message and choose the pushbutton “Output”.
1-2.7 Verify the status, processing date, and transmission time-spot of your messages in
your scheduling agreement.

Delivery schedule
Maintain;
Menu path: Header Messages;
Both messages have a status of “successfully processed” (green light) since they
have been dispatched on explicit request.
The transmission timespots for the messages are given in the columns “Processing
date” and “Time”.
(C) SAP AG IAU210 11-30

IAU210 - Automotive Supplier PDF

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

IAU210 - Automotive Supplier PDF

Загружено:

Авторское право:

Доступные форматы

IAU210 SAP: Automotive: Supplier

Release 1.0 16.01.2004

IAU210 SAP Automotive: Supplier

Copyright 1998 SAP AG. All rights reserved.

Neither this training manual nor any part thereof may

All rights reserved.

Members of automotive supplier project teams, for

The following courses are prerequisites for the IAU210

Note to the user

LO020 4 Days LO235 2 Days

Unit 1 Introduction Unit 6 Production

Unit 2 SD Scheduling Agreement Unit 7 MM Scheduling Agreement

Unit 3 Shipping Activities Unit 8 Internet: Overview

Unit 4 Billing, Credit Memo Procedure Unit 9 What’s Next in Automotive?

Unit 5 Scheduling Agreement

Overview of the automotive logistics chain

Overview of the EDI procedure

(C) SAP AG IAU210 1-1

This course will enable you to understand business

(C) SAP AG IAU210 1-2

At the conclusion of this unit, you will be able

Assign the message types supported under Release

(C) SAP AG IAU210 1-3

This scenario shows typical business

(C) SAP AG IAU210 1-4

Starting from the OEM‘S MM scheduling

(C) SAP AG IAU210 1-5

At the conclusion of this unit, you will be able

Describe the automotive logistics chain, with and

(C) SAP AG IAU210 1-6

Supplier Tier 1 Vehicle Dealer T

From raw material to consumer

(C) SAP AG IAU210 1-7

(C) SAP AG IAU210 1-8

(C) SAP AG IAU210 1-9

(C) SAP AG IAU210 1-10

(C) SAP AG IAU210 1-11

(C) SAP AG IAU210 1-12

Shipping Shipping notification (DESADV) Delivery

Goods receipt Invoice

(C) SAP AG IAU210 1-13

Shipping Shipping notification (DESADV) Delivery

(C) SAP AG IAU210 1-14

doc. 2 Accounting document 1: open item

(C) SAP AG IAU210 1-15

Manufacturer (Sapsota AG) and supplier

(C) SAP AG IAU210 1-16

Delivery note ESA withdrawal

Credit memo Credit memo (GSVERF) Invoice

Accounting Accounting doc.

(C) SAP AG IAU210 1-17

Flexible shop floor control

(C) SAP AG IAU210 1-18

In this topic, you have covered

(C) SAP AG IAU210 1-19

At the conclusion of this unit, you will be able

outline the EDI procedure using the IDoc interface.

assign to business processes the message types

(C) SAP AG IAU210 1-20

(C) SAP AG IAU210 1-21

OEM Tier 1 supplier Tier X supplier

(C) SAP AG IAU210 1-22

OEM Tier 1 supplier Tier X supplier