Logistics Planning
SAP Best Practices Baseline Package
SAP Best Practices
Scenario Overview – 1
Purpose and Benefits:
Purpose

The purpose of logistics planning is to make sure that future demand can be
satisfied by your company’s available resources and to point out situations
where demand cannot be met in time or in the desired quantities.
Benefits

Seamless Integration in complete planning cycle
 CO-PA  SOP  LTP  Demand Planning
Key process flows covered


Sales and Operation Planning
Long Term Planning
Scenario Overview – 2
SAP Applications Required:
Required

SAP enhancement package 4 for SAP ERP 6.0
Company roles involved in process flows

Strategic Planner
Scenario Overview – 3
Detailed Process Description:
Logistics Planning
This process sometimes is called ‘Sales and Operations Planning’. The process usually takes
place in a simulative mode and at an aggregated (usually product group rather than end-item)
level. Once a feasible production plan is found that satisfies demand it can be used as the basis
for operational production planning (MRP and Detailed Capacity Scheduling).
The Best Practice scenarios in this section cover the following planning workflow:

Planning/forecasting of future demand

Aggregated production planning including capacity check in order to check at product group
level if demand can be satisfied (using the SOP functionality)

Transfer of results to Long Term Planning (using the LTP module) to enable
material requirements, based on the production plan (s)

Planning takes place in separate (simulative) planning versions within LTP

Review and adjustments of planned requirements as needed

simulation of
Once the simulated requirements are accepted, the demand (independent requirements) is
then transferred to active demand management for detailed MRP and Production Planning /
Scheduling in the active version.
Process Flow Diagram
Revenue Planner
Event
Logistics Planning
Operational
Production
Planning &
Control
(Production
scenarios)
Periodic Sales
and Operations
Meeting
Sales Qty
Budget and
Transfer to SOP
(with CO-PA),
Revenue
Planning (172)
Sales Quantity
forecast (179)
Strategic Planner
SOP Verification
 Demand Verification
(Check Sales Plan)
 Create Rough-Cut
Production Plan
Transfer Rough
Cut Production
Plan to Inactive
Demand
Management
Create LTP
Planning
Scenario
Evaluate
Capacity
Planning
Execute LTP
MRP
Operative
Productio
n Data
No
Acceptab
le Plan
Yes
CO-PA = Profitability Analysis, SOP = Sales and Operations Planning, LTP = Long Term Planning, MRP = Material Requirements Planning
Copy to Active
Demand
Management
Legend
<Function>
Symbol
Description
Usage
Comments
Band: Identifies a user role, such as Accounts
Payable Clerk or Sales Representative. This band
can also identify an organization unit or group,
rather than a specific role.
Role band
contains tasks
common to that
role.
Symbol
Diagram
Connection
The other process flow symbols in this table go into
these rows. You have as many rows as required to
cover all of the roles in the scenario.
Hardcopy /
Document
External
to SAP
External Events: Contains events that start or end the
scenario, or influence the course of events in the
scenario.
Business
Activity /
Event
Flow line (solid): Line indicates the normal sequence
of steps and direction of flow in the scenario.
Flow line (dashed): Line indicates flow to infrequentlyused or conditional tasks in a scenario. Line can
also lead to documents involved in the process flow.
Connects two
tasks in a
scenario
process or a
non-step event
Business Activity / Event: Identifies an action that
either leads into or out of the scenario, or an outside
Process that happens during the scenario
Does not
correspond to a
task step in the
document
Unit Process: Identifies a task that is covered in a
step-by-step manner in the scenario
Corresponds to
a task step in
the document
SubProcess
Reference
Proces
s
Decisio
n
Usage Comments
To next / From last Diagram: Leads
to the next / previous page of the
Diagram
Flow chart continues on the next /
previous page
Hardcopy / Document: Identifies a
printed document, report, or form
Does not correspond to a task
step in a document; instead, it is
used to reflect a document
generated by a task step; this
shape does not have any outgoing
flow lines
Financial Actuals: Indicates a
financial posting document
Does not correspond to a task
step in a document; instead, it is
used to reflect a document
generated by a task step; this
shape does not have any outgoing
flow lines
Budget Planning: Indicates a
budget planning document
Does not correspond to a task
step in a document; instead, it is
used to reflect a document
generated by a task step; this
shape does not have any outgoing
flow lines
Manual Process: Covers a task
that is manually done
Does not generally correspond to
a task step in a document;
instead, it is used to reflect a task
that is manually performed, such
as unloading a truck in the
warehouse, which affects the
process flow.
Existing Version / Data: This block
covers data that feeds in from an
external process
Does not generally correspond to
a task step in a document;
instead, this shape reflects data
coming from an external source;
this step does not have any
incoming flow lines
System Pass / Fail Decision: This
block covers an automatic
decision made by the software
Does not generally correspond to
a task step in the document;
instead it is used to reflect an
automatic decision by the system
that is made after a step has been
executed.
Financial
Actuals
Budget
Planning
Manual
Proces
s
Unit Process
Process
Reference
Description
Process Reference: If the scenario references another
scenario in total, put the scenario number and name
here.
Sub-Process Reference: If the scenario references
another scenario in part, put the scenario number,
name, and the step numbers from that scenario here
Process Decision: Identifies a decision / branching
point, signifying a choice to be made by the end
user. Lines represent different choices emerging
from different parts of the diamond.
Corresponds to
a task step in
the document
Corresponds to
a task step in
the document
Does not
usually
correspond to a
task step in the
document;
Reflects a
choice to be
made after step
execution
Existing
Version /
Data
System
Pass/F
ail
Decisio
n
Appendix
Master Data Used
Level 1
Plant
1000
00001P001
Products A
Level 2
00001P000100000001
00001P000100000002
00001P000100000003
Products A.01
(MTO)
Products A.02
(MTS)
Parts A.03
Material*:
F226
F100-M1
F1000-P1
Material*:
F126
F29
Material*:
H11
S23
S25
* Not all materials used are
assigned to sample
product groups
CO-PA
SOP Interface
Product Hierarchy
Level 3
Product Group
Level 2
Plant
1000