SCM612 APO Transportation Planning and Vehicle Scheduling (T SCM612
Release 401 27.01.2006
SCM612 APO Transportation Planning and Vehicle Scheduling (TP/VS)................................................................1 Copyright.................................................................................................................................................................2 Course Prerequisites............................................................................................................................................3 Target Audience..................................................................................................................................................4 Course Overview.....................................................................................................................................................1 Course Goal.........................................................................................................................................................2 Course Objectives...............................................................................................................................................3 Course Content....................................................................................................................................................4 Main Business Scenario......................................................................................................................................5 Transportation Processes Overview........................................................................................................................1 Transportation Processes: Unit Objectives.........................................................................................................2 Transportation Processes : Business Scenario....................................................................................................3 Logistics Execution and the Supply Chain.........................................................................................................4 Transportation Management System (TMS).......................................................................................................5 Shipments in R/3 Logistics Execution................................................................................................................7 R/3 Transportation and Shipment Cost Processing.............................................................................................8 R/3 and APO Integration Architecture................................................................................................................9 Transportation Management.............................................................................................................................10 Create Orders in R/3 System.............................................................................................................................11 Transportation Planning: Outbound Process.....................................................................................................12 Transportation Planning: Inbound Process.......................................................................................................13 Transportation Planning: Change Process.........................................................................................................14 Vehicle Scheduling (VS)...................................................................................................................................15 Carrier Selection................................................................................................................................................16 Transfer of Data to R/3......................................................................................................................................17 Transportation Processes : Unit Summary........................................................................................................18 Transportation Processes Overview Exercises..................................................................................................19 Transportation Processes Overview Solutions..................................................................................................21 R/3 Transportation Overview..................................................................................................................................1 R/3 Transportation Processing Overview: Unit Objectives................................................................................2 R/3 Transportation Processing Overview: Business Scenario............................................................................3 Organizational Units in Transportation : Topic Objectives................................................................................4 The Transportation Planning Point.....................................................................................................................6 Route Definition..................................................................................................................................................7 Information in the Route.....................................................................................................................................8 Shipment Document: Topic Objectives..............................................................................................................9 The Shipment Document and its Functions......................................................................................................10 Structure of the Shipment Document................................................................................................................11 Shipment Type..................................................................................................................................................12 Individual Shipment..........................................................................................................................................13 Collective Shipment..........................................................................................................................................14 Transportation Chain.........................................................................................................................................15
Transportation Relevance..................................................................................................................................16 Options for Creating Shipments........................................................................................................................17 Functions in Shipment Processing - Scenarios.................................................................................................18 Shipment Stages................................................................................................................................................19 Deadlines in the Shipment Document...............................................................................................................20 Status Information in the Shipment Document.................................................................................................21 Shipment Costing: Topic Objectives.................................................................................................................22 Shipment Cost Processing in Detail..................................................................................................................23 Requirements for Shipment Cost Calculation...................................................................................................24 Creating a Shipment Cost Document................................................................................................................25 Structure of the Shipment Cost Document........................................................................................................26 Items of the Shipment Cost Document.............................................................................................................27 Overview of Shipment Cost Calculation...........................................................................................................28 Condition Records for Shipment Costs.............................................................................................................29 Shipment Cost Settlement with Direct Transfer...............................................................................................30 Steps During Settlement....................................................................................................................................31 Settings Necessary for Integration: Topic Objectives......................................................................................32 R/3 Customizing and Master Data Activities....................................................................................................33 Transportation Relevance..................................................................................................................................34 Shipment Document Number Ranges...............................................................................................................35 Shipment Type Required Settings.....................................................................................................................36 Transportation Planning Point...........................................................................................................................37 Packaging Materials Needed for APO Mapping...............................................................................................38 Material Master Data Field Checks...................................................................................................................39 R/3 Transportation Processing Overview: Unit Summary................................................................................40 R/3 Transportation Processing Overview Exercises.........................................................................................41 R/3 Transportation Processing Overview Solutions.........................................................................................51 APO Overview........................................................................................................................................................1 APO Overview: Unit Objectives.........................................................................................................................2 APO Overview: Business Scenario.....................................................................................................................3 The Supply Chain: From Supplier to Consumer.................................................................................................4 Key Supply Chain Problems...............................................................................................................................5 SAP's Total Supply Chain Solution....................................................................................................................6 Levels of Supply Chain Management.................................................................................................................7 APO Planning Components................................................................................................................................9 Network Design.................................................................................................................................................10 APO Planning Sequence with R/3 Integration..................................................................................................11 Functions of Demand Planning.........................................................................................................................13 Collaborative Planning in APO.........................................................................................................................14 Supply Network Planning (SNP)......................................................................................................................15 Supply Network Planning Scenario..................................................................................................................16 Comparison of Mid- and Short-Term Planning................................................................................................17
Production Planning / Detailed Scheduling (PP/DS)........................................................................................18 Functions of Production Planning/Detailed Scheduling (PP/DS).....................................................................19 Deployment.......................................................................................................................................................20 Global Available-to-Promise (Global ATP).....................................................................................................21 Transportation Management: Planning Solution...............................................................................................22 APO Planning Process......................................................................................................................................23 Differences Between TLB and TP/VS..............................................................................................................24 Optimization Solutions......................................................................................................................................25 APO Overview: Unit Summary........................................................................................................................26 APO Overview Exercises..................................................................................................................................27 APO Overview Solutions..................................................................................................................................29 APO Integration and Master Data...........................................................................................................................1 APO Integration and Master Data: Objectives....................................................................................................2 APO Integration and Master Data: Business Scenario........................................................................................3 APO Integration: Topic Objectives.....................................................................................................................4 APO Integration (1).............................................................................................................................................5 APO Integration (2).............................................................................................................................................6 APO Integration (3).............................................................................................................................................7 R/3 Plug-In Technology......................................................................................................................................8 RFC: Link Between R/3 and APO......................................................................................................................9 Structure of a RFC Link: Overview..................................................................................................................10 APO Integration with Non-R/3 Systems...........................................................................................................11 APO Master Data: Topic Objectives.................................................................................................................12 Master Data Objects of the CIF.........................................................................................................................13 Initial Data Transfer of Master Data: Overview...............................................................................................14 Generate Integration Model for Initial Data Transfer.......................................................................................15 Activate Integration Model for Initial Data Transfer........................................................................................16 Transfer New APO-Relevant Master Data (1)..................................................................................................17 Transfer New APO-Relevant Master Data (2)..................................................................................................18 Incremental Data Transfer of Master Data (1)..................................................................................................19 Incremental Data Transfer of Master Data (2)..................................................................................................20 Real-Time Transfer of Master Data Changes...................................................................................................21 Transfer Master Data Changes Periodically......................................................................................................22 Integration Model: Other Functions..................................................................................................................23 APO Integration and Master Data : Summary..................................................................................................24 Architecture of Integration Exercises................................................................................................................25 Architecture of Integration Solutions................................................................................................................28 APO TP/VS Master Data........................................................................................................................................1 APO TP/VS Master Data: Unit Objectives.........................................................................................................2 APO TP/VS Master Data: Business Scenario.....................................................................................................3 Vehicle Scheduling Process Flow (1).................................................................................................................4 Master Data: Overview (1)..................................................................................................................................5
Location Types....................................................................................................................................................6 Location Type: Plant...........................................................................................................................................7 Additional Data in APO Location.......................................................................................................................8 Location Type: Distribution Center....................................................................................................................9 Location Type: Customer..................................................................................................................................10 Location Type: Vendor/Carrier/Service Provider.............................................................................................11 External Procurement Relationship...................................................................................................................12 Master Data: Overview (2)................................................................................................................................13 Product Master in APO.....................................................................................................................................14 Product Master Data..........................................................................................................................................15 General Data......................................................................................................................................................16 Maintaining Additional Product Master Fields in APO....................................................................................17 Resources..........................................................................................................................................................18 Transportation Planning Resources...................................................................................................................19 Single Resource Example..................................................................................................................................20 Vehicle Resource Example)..............................................................................................................................21 Transport Method..............................................................................................................................................22 Transportation Lane..........................................................................................................................................23 Transportation Lanes.........................................................................................................................................24 Transportation Lanes.........................................................................................................................................25 TP/VS Supply Chain Modeling - Hierarchies...................................................................................................26 Distance/Duration Calculation..........................................................................................................................27 Transportation Zone (Location) Hierarchy.......................................................................................................28 Carrier Structure Hierarchy...............................................................................................................................29 Hierarchy: Example 1........................................................................................................................................30 Hierarchy: Example 2........................................................................................................................................31 Example: Roundtrip outbound from one location.............................................................................................32 Example: Round trip inbound into one location...............................................................................................33 Example: Mixed round trip to and from one location......................................................................................34 Example: Multi stop - no return........................................................................................................................35 Example: Scheduled vehicles............................................................................................................................36 Note: More complex problems ...can be solved by decomposing the transport network.................................37 APO TP/VS Master Data: Unit Summary.........................................................................................................38 APO TP/VS Master Data Exercises..................................................................................................................39 APO TP/VS Master Data Solutions..................................................................................................................43 Models and Planning Versions................................................................................................................................1 Models and Planning Versions: Unit Objectives................................................................................................2 Models and Planning Versions: Business Scenario............................................................................................3 Models and Planning Versions............................................................................................................................4 Models and Planning Versions for Locations and Products...............................................................................5 Models and Planning Versions for Resources.....................................................................................................6 Supply Chain Engineer (SCE) as the Modeling Tool for Models.......................................................................7
Objects in the Supply Chain Engineer................................................................................................................8 Work Areas in the Supply Chain Engineer.........................................................................................................9 Models and Planning Versions: Unit Summary................................................................................................10 Models and Planning Versions Exercises.........................................................................................................11 Models and Planning Versions Solutions..........................................................................................................13 Transfer of Transaction Data...................................................................................................................................1 Transfer of Transaction Data: Unit Objectives...................................................................................................2 Transfer of Transaction Data: Business Scenario...............................................................................................3 Transaction Data Interface: Core Interface (CIF)...............................................................................................4 Transaction Data Objects of the CIF...................................................................................................................5 Initial Data Transfer of Transaction Data: Overview..........................................................................................6 Integration Model for Transaction Data..............................................................................................................7 Activate Integration Model for Transaction Data...............................................................................................8 Publication of Planning Results..........................................................................................................................9 Distribution Definition......................................................................................................................................10 Transfer of Transaction Data: Unit Summary...................................................................................................11 Transfer of Transaction Data Exercises............................................................................................................12 Transfer of Transaction Data Solutions............................................................................................................17 Monitoring and Error Handling...............................................................................................................................1 Monitoring and Error Handling: Unit Objectives...............................................................................................2 Monitoring and Error Handling: Business Scenario...........................................................................................3 Integration Monitoring........................................................................................................................................4 qRFC Monitor: Motivation.................................................................................................................................5 Using the qRFC Monitor (1)...............................................................................................................................6 Queue Channels for Data Transfer: Example.....................................................................................................7 Using the qRFC Monitor (2)...............................................................................................................................8 Application Log: Motivation...............................................................................................................................9 Using the Application Log (1)..........................................................................................................................10 Using the Application Log (2)..........................................................................................................................11 SCM Queue Manager (1)..................................................................................................................................12 SCM Queue Manager (2)..................................................................................................................................13 qRFC Monitoring: Notification about Exception Messages (1).......................................................................14 qRFC Monitoring: Notification about Exception Messages (2).......................................................................15 Compare/Reconcile Function for Data Inconsistencies in R/3 and APO: Compare.........................................16 Compare/Reconcile Function for Data Inconsistencies in R/3 and APO: Reconcile.......................................17 Monitoring and Error Handling: Unit Summary...............................................................................................18 Vehicle Scheduling (VS): Basic Settings................................................................................................................1 Vehicle Scheduling (VS): Basic Settings: Unit Objectives................................................................................2 Vehicle Scheduling (VS): Basic Settings: Business Scenario............................................................................3 Vehicle Scheduling Process Flow (1).................................................................................................................4 VS General Customizing Activities....................................................................................................................5 Order of Maintenance..........................................................................................................................................6
Geocoding...........................................................................................................................................................7 TP/VS Number Ranges.......................................................................................................................................8 Transportation Mode, Transportation Method, Resources..................................................................................9 Transportation Groups.......................................................................................................................................10 Freight Units......................................................................................................................................................11 Determine Shipment Type................................................................................................................................12 Transportation Matrix, Used for Deadheads.....................................................................................................13 How to maintain a Transportation Matrix.........................................................................................................14 Vehicle Scheduling (VS): Basic Settings: Unit Summary................................................................................15 Vehicle Scheduling (VS): Basic Settings Exercises.........................................................................................16 Vehicle Scheduling (VS): Basic Settings Solutions..........................................................................................23 Vehicle Scheduling (VS).........................................................................................................................................1 Vehicle Scheduling (VS): Unit Objectives.........................................................................................................2 Vehicle Scheduling (VS): Business Scenario.....................................................................................................3 Vehicle Scheduling Process Flow (1).................................................................................................................4 Transactional Exchange relevant for Vehicle Scheduling..................................................................................5 VS Optimizer: How does it work?......................................................................................................................6 VS Optimizer Process.........................................................................................................................................7 Results of an optimization run............................................................................................................................8 Constraints...........................................................................................................................................................9 Costs in Optimization........................................................................................................................................10 Location-Related Costs.....................................................................................................................................11 Penalty Costs: Delayed Delivery and Non-Delivery Costs...............................................................................12 Shipment-Related Costs....................................................................................................................................13 Dimension-Related Costs..................................................................................................................................14 Stopovers, used in Cost Profile.........................................................................................................................15 Costs for Transportation Lane...........................................................................................................................16 Vehicle Scheduling Alert Profile......................................................................................................................17 Optimization Profile (1)....................................................................................................................................18 Planning Horizon...............................................................................................................................................19 Optimization Profile (2)....................................................................................................................................20 Demand Horizon...............................................................................................................................................21 Demand Categories...........................................................................................................................................22 Optimization Profile (3)....................................................................................................................................23 Optimization Profile (4)....................................................................................................................................24 Vehicle Scheduling Consistency Check............................................................................................................25 Interactive Planning (1).....................................................................................................................................26 Interactive Planning (2).....................................................................................................................................27 Create a shipment manually..............................................................................................................................28 Create Shipments Manually..............................................................................................................................29 VS Optimization Run........................................................................................................................................30 Optimization Logfile.........................................................................................................................................31
History of Optimization Runs...........................................................................................................................32 Changing Shipments.........................................................................................................................................33 Deleting Shipments...........................................................................................................................................34 On-Line Scheduling View.................................................................................................................................35 Resource Utilization View................................................................................................................................36 Maintenance of Resource Utilization View......................................................................................................37 Exception Management.....................................................................................................................................38 Set up Alerts for TP/VS....................................................................................................................................39 Vehicle Scheduling Process Flow (4)...............................................................................................................40 Releasing Shipments.........................................................................................................................................41 Communication Layer.......................................................................................................................................42 Publishing Shipments........................................................................................................................................43 Shipment Program (Outbound Process)............................................................................................................45 Shipment Change Process.................................................................................................................................46 End Shipments...................................................................................................................................................47 Archiving Deliveries.........................................................................................................................................48 Archiving Shipments.........................................................................................................................................49 Available Functions for Mass Processing........................................................................................................50 Mass Processing Job Log..................................................................................................................................51 Vehicle Scheduling (VS): Interactive Planning: Unit Summary......................................................................52 Vehicle Scheduling (VS) Exercises..................................................................................................................53 Vehicle Scheduling (VS) Solutions...................................................................................................................63 Carrier Selection......................................................................................................................................................1 Carrier Selection: Unit Objectives......................................................................................................................2 Carrier Selection: Business Scenario..................................................................................................................3 Vehicle Scheduling Process Flow (3).................................................................................................................4 Carrier Selection..................................................................................................................................................5 Manual Carrier Selection....................................................................................................................................6 Automatic Carrier Selection................................................................................................................................7 Carrier Profile......................................................................................................................................................8 Carrier Profile: Carr.sel.......................................................................................................................................9 Carrier Profile: Planning Data...........................................................................................................................10 Carrier Profile: Selection criteria......................................................................................................................11 Selection Strategies...........................................................................................................................................12 Functionality of Automatic Carrier Selection...................................................................................................13 Strategy of the Direct Lane...............................................................................................................................14 Intra-zone Lanes and Carrier Selection.............................................................................................................15 Continuous Move..............................................................................................................................................16 Quotation of Shipments.....................................................................................................................................17 Business Share Configuration...........................................................................................................................18 Vehicle Scheduling Process Flow (5)...............................................................................................................19 TP/VS Tendering...............................................................................................................................................20
Collaborative Transportation Planning: EDI.....................................................................................................21 Bidding Alerts...................................................................................................................................................22 New tendering process after declination...........................................................................................................23 Collaborative Transportation Planning: Internet...............................................................................................24 Collaboration Configuration (Tendering).........................................................................................................25 Shipment Details in a Carrier-Specific Layout.................................................................................................26 Carrier Selection: Unit Summary.....................................................................................................................27 Carrier Selection Exercises...............................................................................................................................28 Carrier Selection Solutions................................................................................................................................31 TP/VS: Additional Topics.......................................................................................................................................1 TP/VS: Additional Topics : Unit Objectives.......................................................................................................2 TP/VS: Additional Topics : Business Scenario...................................................................................................3 Backorder Rescheduling/ Processing..................................................................................................................4 Backorder Processing and Scheduling (1)..........................................................................................................5 Backorder Processing and Scheduling (2)..........................................................................................................6 Backorder Processing and Scheduling (3)..........................................................................................................7 ATP and Transportation Planning.......................................................................................................................8 Direct Update of Batch BOP...............................................................................................................................9 Batch BOP with Postprocessing........................................................................................................................10 Shipment and Transportation Scheduling.........................................................................................................11 Scheduling Process............................................................................................................................................12 Schedules...........................................................................................................................................................13 Schedules (Scenario 1)......................................................................................................................................14 Schedules (Scenario 2)......................................................................................................................................15 Schedules...........................................................................................................................................................16 TP/VS: Additional Topics : Unit Summary......................................................................................................17 TP/VS - Monitoring................................................................................................................................................1 TP/VS – Monitoring: Unit Objectives................................................................................................................2 TP/VS – Monitoring: Business Scenario............................................................................................................3 SAP BW-Definition............................................................................................................................................4 Positioning of BW within the SAP Environment................................................................................................5 Main Topics of BW.............................................................................................................................................6 BW-Architecture.................................................................................................................................................7 Data Process Chain..............................................................................................................................................8 Possible Use of the Business Content.................................................................................................................9 Transportation Content In BW: Overview........................................................................................................10 Example: Freight Cost Reporting Overview (1)...............................................................................................11 Example: Freight Cost Reporting Overview (2)...............................................................................................12 Logistics Content: Outlook...............................................................................................................................13 Definition of Supply Chain Event Management...............................................................................................14 Types of Events and Tracking...........................................................................................................................15 SCEM Example: Procurement Process.............................................................................................................16
SCEM Example: Tracking Pallets for Recall....................................................................................................17 SCEM Scenario.................................................................................................................................................18 Embedded Status Reporting: Example..............................................................................................................19 A Few Application Scenarios for Event Management......................................................................................20 SCEM: Scope and Integration...........................................................................................................................21 TP/VS – Monitoring: Unit Summary................................................................................................................22 Course Objectives...................................................................................................................................................1 Recommended Follow-up Activities...................................................................................................................2 Appendix.................................................................................................................................................................1 Carrier Rates for Carrier Selection Exercise.......................................................................................................2 Freight Rates:......................................................................................................................................................3 Tips and Tricks for APO CIF..............................................................................................................................4 OSS Notes...........................................................................................................................................................5
0 SCM612 APO Transportation Planning and Vehicle Scheduling (TP/VS)
SCM612 APO Transportation Planning / Vehicle Scheduling (TP/VS) SAP AG 2002
R/3 System Release 4.6C and APO Release 3.0A Collection 22 May 2002 Material number
0.2 Copyright
Copyright 2002 S AP AG. All rights re served. No part of thi s publication may be reproduced or transmitted in any form or for any purpose without the express permi ssion of SAP AG. The information contained herein may be changed without prior notice. All rights reserved.
SAP AG 2002
Trademarks: Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. Microsoft®, WINDOWS®, NT®, EXCEL®, Word®, PowerPoint®, and SQL Server® are registered trademarks of Microsoft Corporation. IBM®, DB2®, OS/2®, DB2/6000®, Parallel Sysplex®, MVS/ESA®, RS/6000®, AIX®, S/390®, AS/400®, OS/390®, and OS/400® are registered trademarks of IBM Corporation. ORACLE® is a registered trademark of ORACLE Corporation. INFORMIX®-OnLine for SAP and INFORMIX® Dynamic ServerTM are registered trademarks of Informix Software Incorporated. UNIX®, X/Open®, OSF/1®, and Motif® are registered trademarks of the Open Group. HTML, DHTML, XML, XHTML are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology. JAVA® is a registered trademark of Sun Microsystems, Inc. JAVASCRIPT® is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape. SAP, SAP Logo, R/2, RIVA, R/3, ABAP, SAP ArchiveLink, SAP Business Workflow, WebFlow, SAP EarlyWatch, BAPI, SAPPHIRE, Management Cockpit, mySAP.com Logo, and mySAP.com are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other products mentioned are trademarks or registered trademarks of their respective companies.
0.3 Course Prerequisites
Required Prerequisites:
LO611 Transportation
AP010 APO Overview
Recommended:
Knowledge of Supply Chain Theory
Knowledge of basic transportation planning and execution processes
AP205 APO Master Data Integration
LO610 Delivery Processes
SAP AG 2002
0.4 Target Audience
Participants
Project team members responsible for the implementation of APO TP/VS
SAP consultants and SAP partners
Duration: 3 days
SAP AG 2002
User notes:
These training materials are not a teach-yourself program. They complement the explanations provided by your course instructor. Space is provided on each page for you to note down additional information.
There may not be sufficient time during the course to complete all the exercises. The exercises provide additional examples that are covered during the course. You can also work through these examples in your own time to increase your understanding of the topics.
1 Course Overview
Contents: Course Goal s Course Objective s Course Content Main Busine ss Scenario
SAP AG 2002
(C) SAP AG
SCM612
1
1.2 Course Goal
This course will provide you with: An introduction to the APO tool and its various components An understanding of the Master Data requirements and integration between APO TP/VS and an R/3 System (or other external system) Detailed knowledge of the Transportation Planning/ Vehicle Scheduling (TP/VS) component of APO
SAP AG 2002
(C) SAP AG
SCM612
2
1.3 Course Objectives
At the conclusion of thi s course, you will be able to: Use the TP/VS component of APO to plan both
inbound and outbound shipments. Create the necessary integration models to
communicate data between an R/3 System and the APO TP/VS component. Make the necessary customizing settings
required to perform transportation planning, vehicle scheduling, and carrier selection in the TP/VS environment Use the various monitoring tool s available to
TP/VS
SAP AG 2002
(C) SAP AG
SCM612
3
1.4 Course Content Unit 1 Course Overview Unit 2 Transportation Processes Overview Unit 3 R/3 Transportation Processing Overview
Unit 9 Monitoring and Error Handling Unit 10 Vehicle Scheduling (VS) Basic Settings Unit 11 Vehicle Scheduling (VS)
Unit 4 APO Ove view
Unit 12 Carrier Selection
Unit 5 APO Integration and Master Data
Unit 13 Additional Topics
Unit 6 APO TP/VS Master Data
Unit 15 Conclusion
Unit 14 TP/VS Monitoring
Unit 7 Models and Planning Versions Unit 8 Transfer of Transaction Data
SAP AG 2002
(C) SAP AG
SCM612
4
1.5 Main Business Scenario
As a member of the project team of a company that
manufactures and sells computers and related components, you are responsi ble for the implementation of the APO TP/VS component that is to be interfaced with an SAP R/3 System. Your task i s to integrate the APO TP/VS
environment with your R/3 System by making the necessary customizing settings, creating the Integration models to transfer the necessary ma ster and transaction data, and establishing the TP/VS models to perform the short to intermediate transportation planning for your company.
SAP AG 2002
(C) SAP AG
SCM612
5
2 Transportation Processes Overview
Contents: The Transportation Management System (TMS) R/3 System Logistics processe s Transportation planning and execution with the R/3 System Transportation planning with TP/VS
SAP AG 2002
(C) SAP AG
SCM612
1
2.2 Transportation Processes: Unit Objectives
At the conclusion of thi s uni t, you will be able to: Define processe s related to transportation planning Identify the R/3 System documents that are related to transportation planning Understand planning in the R/3 System vs. planning in APO TP/VS
SAP AG 2002
(C) SAP AG
SCM612
2
2.3 Transportation Processes : Business Scenario
It is important to understand the fundamental business proce sse s related to transportation planning and execution. These processe s must be viewed from a transportation planner’s perspective.
SAP AG 2002
(C) SAP AG
SCM612
3
2.4 Logistics Execution and the Supply Chain Vendor Customer
Warehouse
Border
Production warehouse Distribut ion center
Production facilities SAP AG 2002
The Logistics Execution (LE) component models the logistics processes of a company. It covers the entire process chain from the vendor through the warehouses, production facilities, and distribution centers to the customer. These processes include: The goods receipt process: Goods pickup from the vendor and putaway The goods issue process: Picking and outbound delivery of the goods to the customer Internal warehouse processes such as posting changes, stock transfers, and inventory The transportation process: Inbound and outbound shipments and shipment cost calculation and settlement
(C) SAP AG
SCM612
4
2.5 Transportation Management System (TMS)
APO-TP/VS
BW, SCEM
(Planning)
LES (Execution)
(Monitoring)
SAP AG 2002
Closed feedback loop between planning, execution, and monitoring. Fast and simple information exchange. Monitoring of all processes. Short and long term decision support. Together TP/VS, LES and BW, and Supply Chain Event Management deliver a comprehensive solution for Transportation Management within Supply Chain Management.
(C) SAP AG
SCM612
5
(C) SAP AG
SCM612
6
2.6 Shipments in R/3 Logistics Execution MM ordering
SD order processing
PO processing
Inbound delivery
Vendor
Inbound shipment
Sales order processing
LE Logistics Execution
Goods receipt
Goods issue
Invoice verification
Outbound delivery
Outbound shipment
Customer
Billing
SAP AG 2002
Inbound shipments are an integral part of the process chain in Procurement (MM Purchasing) and are processed based on inbound deliveries. They are required for transportation planning. The basis of the procurement process is the purchase order. The subsequent document is the inbound delivery that is used by the vendor to confirm the delivery. The inbound delivery is an R/3 document and is created with reference to the purchase order. The inbound delivery is the basis for creating the inbound shipment (the shipment of the ordered goods from the vendor to the company's plant). Goods receipt is then posted. Invoice verification completes the purchasing process. The basis of the Sales and Distribution (SD) process is the sales order. The subsequent document is the outbound delivery, which documents the shipping of the goods. Outbound shipments are part of the SD process and are processed based on outbound deliveries. The outbound delivery is the basis for creating the outbound shipment (the shipment of the goods from the company's plant to the customer). Goods issue is then posted and the invoice is created. Shipment documents can also be created for stock transfers between plants.
(C) SAP AG
SCM612
7
2.7 R/3 Transportation and Shipment Cost Processing Transportation processing Create shipment document Process shipment: planning & completion Monitor shipment: lists & shipment info
Shipment cost processing Create shipment cost document Calculate shipment costs Transfer shipment costs; settle with service agent
Bill shipment costs to customer SAP AG 2002
R/3 transportation and shipment cost processing includes transportation processing, shipment cost calculation, and shipment cost settlement. A shipment document is created based on the inbound or outbound deliveries. Other shipment processing activities include shipment planning and completion. The tasks are associated with both planning and executing. Tools are available to support shipment monitoring during planning and execution. They include lists, graphical transportation information, and the transportation information system (TIS). Shipment cost processing begins with the creation of the shipment cost document. The shipment costs are automatically calculated in this document. The costs are transferred so that accruals can be posted and assignments made in Controlling (CO). Settlement is completed with the service agents through the payment of the invoice or creation of a credit memo. You can copy the costs resulting from the shipment and calculated in the shipment cost document into customer billing documents, and thus include the costs of transportation in the customer.
(C) SAP AG
SCM612
8
2.8 R/3 and APO Integration Architecture Materials Management C a r r i e r
B us ines s W a re h o u se
S e t t le
m e n
t P u r c h a s e O r d e r s S t o c k T r a n s p o r t O r d
I m p o r t
FI / CO
L E S F r e i g h t
D a
D
I O
o c u m e
n t a
t i o n F r e i g h t
Transportation C o Processing s t s
Ac c o u n t D e t e r m i n a t i o n F r e i g h t C o s t s
G o o d s
C o s t s
D e l i v e r ie s a n d S h i p m e n t s
A PO TP /V S
I s s u e
Warehouse Management
n b o u n d u t b o u n d
S a l e s
C u s t o m
e r
O
r d e r s
T r ac kin g Supply Chain Se r ve r Event M anager
Sales and Distribution SAP AG 2002
e r s
Foreign t aTrade
S e t t le
m e n t
Integrating APO TP/VS and R/3 provides the ability to perform short to intermediate term transportation planning that optimizes the inbound and outbound transportation demand. In this scenario, TP/VS is used to perform the transportation planning and R/3 is used for transportation execution. Additional functions, such as Event Manager and Business Warehouse reporting, can be provided in the R/3 and APO architecture.
(C) SAP AG
SCM612
9
2.9 Transportation Management Shipper
Shipper /C arrier
Carrier
Creat e Orders
Vehicle Scheduling
Creat e Planned Shipments Including Planned Deliveries Exchange Transportation Requirements Carrie CarrierrSelection/ Selection/ Tendering Tendering
Routing/Scheduling
Collaborate on Exceptions Vehicle VehicleScheduling/ Scheduling/ Transfer TransferDat Dataato to R/3 R/3 Execute Shipment
SAP AG 2002
The target of the transportation planning process is to optimize the inbound or outbound transportation demand between a plant/DC and different other locations, such as suppliers and customers. The optimization covers the company’s own fleet as well as carrier vehicles. Carrier selection can be executed to select carriers based on least cost, business share, or priority. The Transportation Management scenario comprises the following main processes: Document entry Consolidation of transportation demand Interactive Vehicle Scheduling Carrier Selection Collaborative Transportation Planning Transfer Deliveries and Shipments to R/3 Execute Shipment in R/3 by picking and packing deliveries, goods issue posting, set status shipment end, and archive shipments
(C) SAP AG
SCM612
10
2.10 Create Orders in R/3 System Shipper
Shipper /C arrier
Carrier
Creat e Orders
Vehicle Scheduling
Creat e Planned Shipments incl. Planned Deliveries Exchange Transportation Requirements Carrier Carrie rSelection/ Selection/ Tendering Tendering
Routing/Scheduling
Collaborate on Exceptions Vehicle VehicleScheduling/ Scheduling/ Transfer TransferDat Dataato to R/3 R/3
Routing/Scheduling
Execute Shipment
SAP AG 2002
Different types of orders are first created in the R/3 system. These orders (sales orders, purchase orders, stock transfer orders, and so on) build the transportation demand for APO TP/VS. Delivery and Shipment documents created in the R/3 system can also be used to build the transportation demand. The transportation demand can be transferred from R/3 via integration model (CIF) into APO or is generated directly in the APO system (for example, as a result of the TLB run). The ATP check is performed out of the R/3 into APO for sales orders. Additional data is brought over from R/3 to APO and stored in database tables. This additional information can then be used in the TMSprocess for special handling, instructions, compatibilities, and so on.
(C) SAP AG
SCM612
11
2.11 Transportation Planning: Outbound Process
Create
Demands at Locations Plan material and source
Planned Delivery Items
Add. Data
- Selection - Consolidation, scheduling, and building planned shipments
Checks
Deliveries Add. Data Checks
Shipment with Deliveries
- Rescheduling of orders
Create
- Carrier Selection
Update
Create Update
Mid- and short-term optimization
Orders
Planned Shipments including Planned Deliveries resp. Planned Delivery Items
SAP AG 2002
Sales orders, outbound deliveries, and shipments can be used to create transportation demand in TP/VS. Using sales order data, TP/VS planning process creates planned delivery and shipment documents in the R/3 system. The TP/VS planning process does not make any changes to the sales documents in the R/3 system. Generally, transportation-related changes made to an R/3 document are updated in the corresponding TP/VS document.
(C) SAP AG
SCM612
12
2.12 Transportation Planning: Inbound Process
Create
Demands
Add. Data
Production planning and sourcing
Checks
Purchase Orders
Add. Data
Create Update
Planned Delivery Items / Purchase requisitions Group according to planned shipments
Checks
Deliveries
Create Update
Planned Shipments including Planned Deliveries
Add. Data Create Checks
Shipment with Deliveries
Mid and short-term optimization
Purchase Requisiton
Update
SAP AG 2002
Purchase Orders, Stock Transport Orders, Inbound Deliveries, and Shipment documents are used to plan inbound transportation demand. When Purchase Orders/Stock Transport Orders are provided to TP/VS for planning, TP/VS will create the Inbound Delivery and Inbound Shipment document data for the R/3 System. Transportation demands from Supply Network Planning (SNP) are also created in TP/VS for planning. Transportation-relevant changes made to an R/3 document are updated in the corresponding TP/VS document.
(C) SAP AG
SCM612
13
2.13 Transportation Planning: Change Process
Orders
Update
Demands
Manual changes
Deliveries
Update
Planned Deliveries
Update
Manual changes
Shipment with Deliveries
New optimization run
Update
Planned Shipments and Planned Deliveries
Update
SAP AG 2002
Transportation planning-relevant changes made to any R/3 document that has a corresponding TP/VS document are made to those documents. A shipment in the APO system changes its status if you change documents in the R/3 System that are contained in a planned shipment in the APO System. Note: You can find a process list with the expected behavior of the APO System when changing the planning objects in the OLTP system in note 362445.
(C) SAP AG
SCM612
14
2.14 Vehicle Scheduling (VS) Shipper
Shipper /C arrier
Carrier
Consolidation of transportation demand in APO TP/VS
Creat e Orders
Assignment of orders to vehicle resources, manually or using the optimizer
Vehicle Scheduling
Creat e Planned Shipments including Planned Deliveries Exchange Transportation Requirements Carrie CarrierrSelection/ Selection/ Tendering Tendering
Transfer orders into planned shipments
Routing/Scheduling
Collaborate on Exceptions Vehicle VehicleScheduling/ Scheduling/ Transfer TransferDat Dataato to R/3 R/3
Routing/Scheduling
Execute Shipment
SAP AG 2002
The
next step is the consolidation of transportation demand in APO. In the unassigned freight units view in the vehicle scheduling planning board the transportation demand (sales orders, purchase orders, and stock transfer orders) is visible. The orders in this area are not assigned to a resource and have to be planned now. There are two ways to assign the transportation demand to the resources, manually and by using the optimizer. To assign a transportation demand manually to a vehicle resource you have to select the relevant resource first and then choose the unassigned orders which you want to plan on this resource. The optimizer takes all unassigned orders and unreleased shipments into consideration. The following criteria is taken into account: Departure from and return to depot Loading and unloading time Order consolidation Cost minimization of shipment time Cost minimization of distance Costs for earliness/delay Costs for non-delivery Shipment fixed costs The resources are planned now and the orders are changed into planned shipments.
(C) SAP AG
SCM612
15
2.15 Carrier Selection Shipper
Shipper /C arrier
Carrier
Assignment of shipments to carrier Manually or using a carrier selection profile
Creat e Orders
Vehicle Scheduling
Creat e Planned Shipments incl. Planned Deliveries Exchange Transportation Requirements Carrie r Selection/ Tendering
Routing/Scheduling
Collaborate on Exceptions Vehicle VehicleScheduling/ Scheduling/ Transfer TransferDat Dataato to R/3 R/3
Routing/Scheduling
Execute Shipment
SAP AG 2002
After the planning is settled, the planned shipments are assigned to certain carriers. The carrier selection is executed manually for each carrier or automatically via a selection profile containing several carriers. Carrier selection Checks availability and compatibilities Processes: Cost-based: Rules of freight cost engine will be taken from LES or you can maintain costs in the APO system on the transportation lane Business share: Balancing of business share to fulfill contracts Priorities: Carrier with high priority will be chosen User can choose the sequence of processes After the carrier selection is done the shipments are ready to be released or published. Publication allows the planning result to be accepted as final and the shipment is prepared for transfer to the OLTP system. Released shipments will not be deleted when doing a new optimization run.
(C) SAP AG
SCM612
16
2.16 Transfer of Data to R/3 Shipper
Shipper /C arrier
Carrier
The transfer is triggered from the Interactive Vehicle Scheduling Board via the GOTO-functions Transfer deliveries to R/3: GOTO OLTP generation of deliveries
Creat e Orders
Prepare shipment transfer: GOTO Check release of planned shipments
Vehicle Scheduling
Transfer shipments to R/3: GOTO Transfer planned shipments to OLTP
Creat e Planned Shipments incl. Planned Deliveries Exchange Transportation Requirements Carrie r Selection/ Tendering
Routing/Scheduling
Collaborate on Exceptions Vehicle Scheduling/ Transfer Dat a to R/3
Routing/Scheduling
Execute Shipment
SAP AG 2002
After releasing the shipments, the OLTP transfer of deliveries and shipments is enabled. Now the transfer of the planned shipments to the R/3 System can be triggered from the interactive vehicle scheduling board.
(C) SAP AG
SCM612
17
2.17 Transportation Processes : Unit Summary
You are now able to: De scribe proce sse s related to transportation planning Identify the R/3 System documents that are related to transportation planning Understand planning in the R/3 System vs. planning in APO TP/VS
SAP AG 2002
(C) SAP AG
SCM612
18
2.18Exercises Unit: Transportation Processes Overview
At the conclusion of this exercise, you will be able to: •
Describe the Transportation Management System functions.
•
List the documents that are used in the TMS components.
•
Outline the functions provided by the APO TP/VS planning component.
A business’ transportation functions can be divided into two fundamental steps: planning and execution. In an R/3 (OLTP) and APO environment, the planning step is carried out in APO and the execution step is performed in the R/3 (OLTP) System. It is important to understand the functions provided in each system, in order to perform these steps. 1-1
Select the process(es) that are not part of the Logistics Execution (LE) component of R/3: a) Transportation process b) Internal warehouse process c) Material Requirements Planning (MRP) d) Goods issue process e) Goods receipt process f) Production Planning process
1-2
_______________________ shipments are an integral part of the process chain in Procurement and are created from __________________ ________________ documents.
1-3
_______________________ shipments are created from _______________________ delivery documents that are generated from sales orders.
1-4
True or False. Delivery documents must be created before shipment documents can be created.
1-5
True or False. Shipment costing is required for each shipment document.
(C) SAP AG
SCM612
19
1-6
R/3 transportation and shipment cost processing includes: a) _________________________________________________________ b) _________________________________________________________ c) _________________________________________________________
1-7
True or False. The goal of the transportation planning process is to optimize the inbound and outbound transportation demand between the plant/DC and other locations such as customers, suppliers and other plants/DC’s.
1-8
Which of the following criteria does the TP/VS Optimizer take into account during transportation planning: a) Shipment fixed costs b) Cost minimization of distance c) Order consolidation d) Loading and unloading time e) Cost minimization of distance f) Goods issue date g) Costs for non-delivery h) Distance in the delivery route code
1-9
During Carrier Selection, TP/VS can select carriers based on the following: a) Vehicle capacities (weight, volume, number of pallets, and so on) b) Availability and compatibility of products c) Contract terms d) Priority of carrier e) Business share f) Carrier quality / service performance rating g) Costs
1-10
True or False. Sales order and Purchase order demand must be used for APO TP/VS planning of outbound and inbound shipments, respectively.
1-11
What function triggers the transfer of planned deliveries and shipments?
(C) SAP AG
SCM612
20
2.19Solutions Unit: Transportation Processes Overview
1-1
Select the process(es) that are not part of the Logistics Execution (LE) component of R/3: Material Requirements Planning and the Production Planning process are not part of the LE component.
1-2
Inbound shipments are an integral part of the process chain in Procurement and are created from Inbound Delivery documents.
1-3
Outbound shipments are created from Outbound delivery documents that are generated from sales orders.
1-4
True. Delivery documents must be created before shipment documents can be created.
1-5
False. Shipment costing is not required for each shipment document.
1-6
R/3 transportation and shipment cost processing includes: a) Transportation processing b) Shipment cost calculation c) Shipment cost settlement
1-7
(C) SAP AG
True. The goal of the transportation planning process is to optimize the inbound and outbound transportation demand between the plant/DC and other locations such as customers, suppliers, and other plants/DCs.
SCM612
21
1-8
Which of the following criteria does the TP/VS Optimizer take into account during transportation planning: a) Shipment fixed costs b) Cost minimization of distance c) Order consolidation d)Loading and unloading time e) Cost minimization of distance g) Costs for non-delivery
1-9
During Carrier Selection, TP/VS can select carriers based on the following: a) Vehicle capacities (weight, volume, number of pallets, and so on) b) Availability and compatibility of products d) Priority of carrier e) Business share g) Costs
1-10
False. Sales order and Purchase order demand does not have to be used for APO TP/VS planning of outbound and inbound shipments, respectively.
1-11
The transfer of planned deliveries and shipments are triggered by the GOTO function.
(C) SAP AG
SCM612
22
3 R/3 Transportation Overview
Contents: Organizational Units in Transportation Shipment document structure and control Shipment costing Ba sic R/3 to APO TP/VS interface settings
SAP AG 2002
(C) SAP AG
SCM612
1
3.2 R/3 Transportation Processing Overview: Unit Objectives At the conclusion of thi s uni t, you will be able to: Explain the organizational units related to R/3 System transportation De scribe the structure of the shipment document and its functions Identify and locate important information in the shipment document De scribe the processe s related to R/3 System freight costing Explain the purpose, structure and processe s related to the shipment cost document Make the basic customizing and master data settings to interface an R/3 System with an APO TP/VS System SAP AG 2002
(C) SAP AG
SCM612
2
3.3 R/3 Transportation Processing Overview: Business Scenario
The computer manufacturer will utilize the APO TP/VS component to plan shipments for goods to be received from suppliers and to be shipped to its customers. Although the planning function i s done using TP/VS, the execution of the shipments will be made using the R/3 transportation application. The primary document used in these proce sse s i s the shipment document. Project team members have to understand its structure, functions, and the information it contains. The manufacturer will also use the R/3 System shipment costing function to compute the freight costs related to the shipments. SAP AG 2002
(C) SAP AG
SCM612
3
3.4 Organizational Units in Transportation : Topic Objectives
At the conclusion of thi s topic, you will be able to: Name the organizational units that are used in
R/3 System transportation proce ssi ng and execution
SAP AG 2002
(C) SAP AG
SCM612
4
(C) SAP AG
SCM612
5
3.5 The Transportation Planning Point
Transportation planning points
Company code
Planning and processing shipments
1010 Hamburg International shipment by sea
1011 Hamburg Rail shipments
1200 Dresden Truck Shipments
SAP AG 2002
The transportation planning point is the central point within the company that plans, processes, and monitors shipments. It can be a location or a group of people responsible for processing. Each shipment is created and processed by a single transportation planning point. You can freely define the transportation planning points to meet your corporate requirements (for example, in terms of the location or the mode of transport). The transportation planning point is defined for a specific company code in Customizing. This assignment of the planning point to the company code is important for shipment cost calculation and settlement.
(C) SAP AG
SCM612
6
3.6 Route Definition
Cologne
Frankfurt
Trade Trade center center
Praha Prague
Route Route Stage Stage Nuremberg
Border Straßbourg Strasbourg
Vienna Munich
SAP AG 2002
A route is the journey to be covered between a departure point and a destination and is represented by the route code. A route can be defined in great detail and consist of one or more individual stages, but it can also be a general description or even simply a destination area. Like a shipment stage, a stage can be a leg, a load transfer point, or a border crossing point. For example, the above route consists of five stages: three legs, one load transfer point, and one border crossing point. The route code is determined for each line item in a sales order and is copied into the header of the outbound delivery document(s) created from the sales order. Inbound delivery documents do not require a route code, but one may be entered manually. The route code is not used by APO TP/VS because TP/VS determines the route stages based on the planning criteria associated with transportation lanes. Routes in the R/3 System are only required to identify the transportation documents as relevant for shipment. Multimode APO transports or APO transports with transshipment points are created with several shipment stages in the R/3 System. In the R/3 System they are identified as generated manually. A transfer of the routes from the R/3 System to the APO System does not occur. Currently a report or something similar is not available.
(C) SAP AG
SCM612
7
3.7 Information in the Route
De scription Di stance
Service agent
Route Transportation relevance
Factory calendar
Transit time
Shipping type Transportation planning lead time
Travel duration
SAP AG 2002
You may define routes in Customizing or in LE master data maintenance. A route code can contain a number of fields of information that are important to the shipment (for example, distance, transportation lead time, travel duration, shipping type, and service agent). When TP/VS is used for transportation planning, it will determine the route itinerary. Predefined stages are not necessary for the route and should not be copied into the shipment document. You set transportation relevance for the route in Customizing for Transportation. The route must be set for transportation relevance if it is used in sales orders and deliveries planned in TP/VS.
(C) SAP AG
SCM612
8
3.8 Shipment Document: Topic Objectives
At the conclusion of thi s topic, you will be able to: Define the structure of the shipment document De scribe the role of the shipment type List the basic shipment type s Identify key information fields in the shipment
document Explain the ways a shipment document can be
created
SAP AG 2002
(C) SAP AG
SCM612
9
3.9 The Shipment Document and its Functions Grouping of inbound or outbound deliveries in shipments Create output (EDI / documents)
rrtt poo SSeer nnssp rvvi a a r iccee ff tt r aagg ee oo eenn d d o o tt M M
Record shipment characteristics
Shipment document functions Record planned and actual dates/status information Plan
Act.
Determ ine shipment stages A
C
Packing/loading B
04.06. 12.06.
SAP AG 2002
The shipment document is the central document that is used to model shipments in the R/3 System. It contains all information necessary for organizing and carrying out a shipment. The shipment document provides the following functions: Combining inbound deliveries to form inbound shipments Combining outbound deliveries to form outbound shipments Assigning service agents, modes of transport, shipment types, and so on Planning and monitoring deadlines Specifying shipment stages Cross-delivery packing and creation of shipping units Creating output and shipping papers Recording shipment-relevant texts Recording partner information Using TP/VS, shipments are created by combining deliveries within APO. Carriers and transportation methods are also assigned to the shipments. They are then transferred to the R/3 System. In the R/3 System, they contain the data maintained in APO.
(C) SAP AG
SCM612
10
3.10 Structure of the Shipment Document
Shipments and deliveries
0000001234
Service agent TPPt:
Nords peed
ShPt
1000
Shipment header: Wt/kg
General data for the entire shipment
18,586 0
0080004903
1200
8,386
0080004879
1000
3,200
0080004905
1000
Items:
Inbound or outbound 7,000 deliveries in the shipment
SAP AG 2002
The shipment document contains general data that applies to the whole document, such as shipment type, transportation planning point, route, deadlines, and status information. This information is displayed in the shipment header. Since the shipment is a collection of inbound or outbound deliveries that are shipped together, the items of the shipment correspond exactly to the inbound deliveries in the case of inbound shipments, and to the outbound deliveries in the case of outbound shipments.
(C) SAP AG
SCM612
11
3.11 Shipment Type
Completion type
Leg determ ination/stage selection
Number assignment
Leg indicator
Texts
Shipment Shipment type type Output
Shipping type
Copying rule
Update change documents?
Planning Profile Split profile SAP AG 2002
The shipment type controls elements in the shipment document and represents a particular processing type for a shipment. Shipment type settings include: The leg determination type (automatic leg determination, for example) The completion type (loaded outbound shipment and inbound shipment, for example) The processing control (collective shipment using one mode of transport, for example) The service level (general cargo and grouped load, for example) The shipping type (truck, train, and mail, for example) The leg indicator (preliminary leg, subsequent leg, direct leg, for example) Copying data from preceding documents (unique forwarding agent and route, for example) Output determination and text determination procedure Default values for the shipment document (weight and volume unit and planning profile, for example) You can define your own shipment types to suit your own shipment requirements. Shipment types created for APO TP/VS use must not have leg determination enabled.
(C) SAP AG
SCM612
12
3.12 Individual Shipment
SHIPMENT Hamburg DELIVERY 1 From : Hamburg
Delivery 1,2
To: Frankfurt
BA
Load : A
DELIVERY 2
Frankfurt
From : Hamburg To: Frankfurt Load : B
SAP AG 2002
An individual shipment has the following characteristics: One or more inbound or outbound deliveries are involved in the shipment There is one single point of departure and one single destination In most cases, only one mode of transport is used A shipment document is created In the standard system, shipment type 0001 is predefined. Important control parameters in Customizing include: Completion type: one = Loaded outbound shipment Processing control: one = Individual shipment using one mode of transport Leg indicator: four = Direct leg
(C) SAP AG
SCM612
13
3.13 Collective Shipment
SHIPMENT Hamburg DELIVERY 1
BA
From : Hamburg
Delivery 1.2
To: Stuttgart Load : A
Frankfurt
A
DELIVERY 2 From : Hamburg
Delivery 1
To: Frankfurt
Stuttgart
Load : B
SAP AG 2002
A collective shipment has the following characteristics: One or more inbound or outbound deliveries are involved in the shipment There are one or more points of departure and one or more destinations In most cases, only one mode of transport is used A shipment document is created In the standard system, shipment type 0002 is predefined. Important control parameters in Customizing include: Completion type: one = Loaded outbound shipment Processing control: three = Collective shipment using one mode of transport Leg indicator: four = Direct leg
(C) SAP AG
SCM612
14
3.14 Transportation Chain Dresden
Hamburg
Rotterdam
New York Harbor
Boston
Philadelphia
Shipment 1 Delivery 1.2 Shipment 2
Delivery 3-6
Preliminary legs
Main leg Shipment 3
Subsequent legs Shipment 4
Delivery 1-6
Delivery 1.2 Shipment 5 Delivery 3 Shipment 6 Delivery 4-6
SAP AG 2002
A transportation chain supports the shipment of inbound or outbound deliveries for which several modes of transport are to be used. This means that the deliveries are involved in various subsequent shipments. A transportation chain has the following characteristics: One or more deliveries are involved in several shipments. There are one or more points of departure and one or more destinations. Various modes of transport can be used. Several shipment documents are created: preliminary legs, main legs, and subsequent legs. Special shipment types are available for this in the system. Example of a transportation chain: The computer manufacturer ships deliveries from Dresden and Hamburg to Boston and Philadelphia The deliveries from Dresden and Hamburg are shipped separately by truck or rail to Rotterdam: Leg indicator one = Preliminary leg In Rotterdam, the deliveries are loaded together and shipped to New York: Leg indicator two = Main leg In New York, the deliveries are again shipped separately by truck to Boston and by rail to Philadelphia: Leg indicator three = Subsequent leg APO TP/VS does not support the creation of transportation chains; however, various multi-modal shipment scenarios can be modeled by TP/VS.
(C) SAP AG
SCM612
15
3.15 Transportation Relevance
Delivery item category
Delivery type Out. delivery LF Cash sale
✔
BV
Out. delivery EL
✔
Route of the delivery
Standard item TAN ✔
Route HH - F
✔
Text item
Route HH - M
✔
TATX
Out. delivery ELN
✔
Northern route
Out. delivery LF Route HH - F Transportation planning status = A SAP AG 2002
The transportation relevance of the delivery type, the delivery item category, and the route in the delivery controls whether or not a shipment can be created. The delivery type must be set as relevant for transportation so that a shipment can be created. Similarly, at least one delivery item category in the delivery must be relevant for transportation. The outbound delivery must contain a route code that is relevant for transportation (does not apply to inbound deliveries). A route is defined as the connection between a point of departure and a destination point, with several possible points in between. If all three (or two in the case of inbound deliveries) conditions are met, the delivery has transportation planning status A, which means that the delivery document is relevant for transportation. You set transportation relevance in Customizing for Transportation.
(C) SAP AG
SCM612
16
3.16 Options for Creating Shipments Creating shipments
Manually using Create Shipment
Without planning proposal
With planning proposal
Automatically in collective proce ssing using the worklist
Using a transportation planning system
TP/VS Online
B/ground
R/3
SAP AG 2002
The R/3 System contains different ways of creating shipments: You can create shipments manually using the Create shipment function. You can select deliveries due for shipping using different selection criteria and create the documents manually. You can also use a planning proposal. This is a predefined profile whose rules specify that deliveries are automatically combined into shipments and completed with data. The system can also create shipments automatically. To do this, use a collective processing run that is executed online or in batch mode. The system creates one or more shipment documents according to different processing rules. If the shipments are created and optimized by an external transportation planning system such as APO TP/VS, you can link to this system with an interface. In the R/3 to APO environment, this interface is called the Core Interface (CIF).
(C) SAP AG
SCM612
17
3.17 Functions in Shipment Processing - Scenarios
Determ ining and commissioning the service agent
Scheduling deadlines
Determ ining the stages Determ ining the means of transport
Entering texts / comments
Checking in the means of transport Printing documents/ generating output
Posting goods issue
Loading the means of transport Creating billing documents based on the deliveries
SAP AG 2002
Depending on the type of shipment, you may need to process the created shipment documents further. Using shipment processing in the R/3 System, you can perform these activities and record related information in the shipment document. Most of the activities are optional. Depending on your requirements, you may actually use onlysome of them. Part of the information in shipment processing can be determined based on the shipment type (for example, means of transport) or is adopted from the deliveries (for example, shipping units, service agent, route, and route stages). You can usually change this information manually. Determine other data in the shipment document (for example, deadlines, notes, texts, and so on).
(C) SAP AG
SCM612
18
3.18 Shipment Stages Leg Rotterdam
New York
Partner: Forwarding agent
Load transfer point
Border crossing point
New York
Rotterdam
Partner: Load. supervisor
Partner: Customs agent
Stop Cus to ms
SAP AG 2002
Stages contain information on the geographical characteristics of a shipment. This information is frequently used as a basis for calculating shipment costs. The system differentiates between the following stage types: Leg: A connection between a starting point and an end point. The starting and end points can be a transportation connection point, a shipping point, an unloading point at the customer's or vendor's site, and so on. Load transfer point: Location/point where a shipment is loaded/unloaded or transferred from one means of transport to another. Border crossing point: Location/point where a shipment crosses the border. For each stage, you can record information, such as the responsible service agent, deadlines, distance, shipment cost relevance, freight code, and so on. You can also assign the deliveries to the individual stages. Using APO TP/VS planning, TP/VS will automatically assign the deliveries selected for a shipment to the stages that are determined by TP/VS.
(C) SAP AG
SCM612
19
3.19 Deadlines in the Shipment Document MO 1 8 15 21 28
TU 2 9 16 22 29
WE TH 3 4 10 11 17 18 23 24 30 31
FR 5 12 19 25
SA 6 13 20 26
SU 7 14 21 27
Deadlines in shipment header
Deadlines in shipment
Deadlines per stage
Planned/actual deadlines:
Planned/actual deadlines:
Planned Check-in Loading start Loading end Shipment completion Shipment start Shipment end
Stage start Stage end
11 10 9 8
12
1
7 6 5
2 3 4
Other deadlines (header level) Operation Planned deadlines Actual deadline Reason for deviation Locations and so on
SAP AG 2002
You can record the times and deadlines for planning and executing the transportation activities in the shipment document. For standard activities, such as planning, check-in, loading, processing, shipment start and shipment end, you can record planned and actual deadlines in the shipment document at header level. You can also specify exact times for the deadlines. You can also define planned and actual start and end dates for each shipment stage. Similar to Shipping, you can specify additional individual deadlines that are used for further controlling shipment processes. Besides planned and actual deadlines and times, you can also enter operation types, reasons for deviations and locations (points). You can define a deadline procedure (network profile) for your individual deadlines for each shipment document type.
(C) SAP AG
SCM612
20
3.20 Status Information in the Shipment Document
Processing status of shipment
Status information in the shipment document header: Overall status Planned Check-in
Check-in
✔ ✔
Completed Completed
Loading start
Not completed
Loading end
Not completed
Shipment completion
Not completed
Shipment start
Not completed
Shipment end
Not completed
SAP AG 2002
When transportation activities such as planning, checking in, loading, and so on, are finished, you can set a status. As soon as the status is set, the activity is considered completed. You always know the current processing status of a shipment and can quickly provide information. You can set the status by: Choosing the corresponding pushbutton; the current date is adopted as the actual date. Entering the actual date; the status is then set by the system. A traffic light symbol displays the overall status of the shipment. Red: Planned status is set. Yellow: Check-in/Loading Start/Loading End status is set Green: Shipment completion/Shipment Start/Shipment End status is set Note: For shipment cost calculation, the status Planned must be set as a minimum. Note: The planned status is automatically set if you transfer shipments from TP/VS to R/3.
(C) SAP AG
SCM612
21
3.21 Shipment Costing: Topic Objectives
At the conclusion of thi s topic, you will be able to: De scribe the shipment costing process List the requirements of shipment cost
calculation Explain the structure of the shipment cost
document Understand the shipment costing settlement
proce ss
SAP AG 2002
(C) SAP AG
SCM612
22
3.22 Shipment Cost Processing in Detail
Shipment
Shipment cost document 1. Calculate shipment costs 2,316.- USD 2. Assign shipment costs to account A
3. Transfer shipment costs
XX
B XX
4. Settle shipment costs
SAP AG 2002
Shipment cost calculation and shipment cost settlement are available for both outbound and inbound shipments. The shipment costs are recorded in a new system document called the shipment cost document. You perform the following functions from within this document: Calculate the shipment costs Account assignment: Assign the costs in Financial Accounting and Controlling Transfer the costs to FI and CO Settle the costs with the service agent
(C) SAP AG
SCM612
23
3.23 Requirements for Shipment Cost Calculation
Shipment
The shipment document must be shipment cost relevant
ShpmntCostsRel. ✔
The shipment document must have the necessary overall status, (planned status at the very least)
Status Planned
✔ Completed
SAP AG 2002
A shipment must be relevant for shipment costs (at header and/or stage level) in order to create a shipment cost document for a shipment. The shipment must also have the required overall status set in the definition of the shipment cost type. As a minimum, it must have Planned status. Execute the following in Customizing: Define number ranges for the shipment costs. Define and assign shipment cost types and item categories. For each shipment type, you must set shipment cost relevance for the following shipment elements: header, leg, border crossing point, and load transfer point.
(C) SAP AG
SCM612
24
3.24 Creating a Shipment Cost Document
Shipment document
Shipment cost document
1
1
2
2
3
3
1:1
SAP AG 2002
You can create shipment cost documents individually in dialog mode or using collective processing. If you create an individual shipment cost document, always directly refer to a shipment document. Create exactly one shipment cost document for each shipment document. As a result, there is a 1:1 relationship between the two documents. Depending on your settings, the system automatically calculates the shipment costs, assigns them to an account, and transfers them to Financial Accounting when you create the shipment cost document.
(C) SAP AG
SCM612
25
3.25 Structure of the Shipment Cost Document Shipment cost docum ent • Overall status • Reference data • Adm inistrative data
Header
• Item status • Pricing procedure • Determ ined pricing date • Tax data • Settlement data • Service procurement
Item 1 Sub-item 1 Item 2 Sub-item 1
Result of shipment cost calculation
Sub-item 2 SAP AG 2002
The shipment cost document consists of the following sections: Shipment cost header The shipment cost header contains general information on the entire document. Status, reference, and administrative information is provided. The status is a cumulated status derived from the individual items. Shipment cost item The items contain general data for shipment cost calculation and settlement, such as service agent, pricing and settlement date, tax amount and tax base amount, and organizational data such as company code, plant, and purchasing organization. Each item has its own status for the shipment cost calculation, account assignment, and transfer functions. Shipment cost sub-item Shipment costs are calculated at shipment cost sub-item level. The calculation result is also recorded at this level.
(C) SAP AG
SCM612
26
3.26 Items of the Shipment Cost Document
Shipment
Shipment costs
Header
1. Item Insurance ABC Insur ance
Stage 1
2. Item
Hamburg - Frankfurt Nordspeed for ward ing agent
Stage 2
3. Item
Frankfurt - Stuttgart Schmal enbach forward ing agent
SAP AG 2002
The shipment cost items either refer to the shipment header or to a shipment stage. For example, an item that refers to the header can include insurance charges for shipment insurance. An item that refers to a shipment stage can include load transfer costs. The function of the items is controlled through the item category. The items can be automatically generated or manually created depending on the Customizing settings.
(C) SAP AG
SCM612
27
3.27 Overview of Shipment Cost Calculation Pricing procedure 1. Basic freight
FB00
2. Discount 1
FD00
3. Discount 2
FD10
Shipment costs From NY to WA Conditions
10 t
FB00 Basic freight 1100 USD FD00 Discount 1 -100 USD FD10 Discount 2 -5 %
Condition type FB00 Access sequence:MATK Access sequence:MATK Condition tables: 1. Service agent/tariff zone/ freight class 2. Service agent/tariff zone Records for cond. type FB00 No valid record available Valid record available
Scale 1300 USD 1 t or more 1100 USD 10 t or more 1000 USD 20 t or more
SAP AG 2002
In this example, 10 tons of a material are shipped by a forwarding agent from New York to Washington. The system determines the shipment costs automatically. The system first determines the corresponding pricing procedure. This contains every possible condition type within shipment pricing in a particular sequence. The system reads the first condition type in the pricing procedure. The condition type identifies the characteristics of a condition. For this condition type, the system determines the assigned access sequence. The system reads the access sequence. In the sequence, the condition tables are accessed at least once. The sequence of the condition tables constitutes the search strategy to determine the corresponding condition record. The system searches for valid condition records for the condition tables (accesses). A condition record contains the actual shipment rates. If no valid condition record exists for the first condition table, the system searches for condition records for the second table. When the system finds a valid condition record for a condition table, the condition record is read and the corresponding value is copied into the shipment cost document. The system repeats all of these steps for each condition type until the entire pricing procedure is processed.
(C) SAP AG
SCM612
28
3.28 Condition Records for Shipment Costs
Level at which the condition is defined
Condition type :
FB00 Basic freight
Service agent:
1120
Tariff zone - departure:
DE20
Tariff zone - destination: DE80 Freight class:
B
Validity period 07/01/1999 - 12/31/2002 Scale: to 1000 lb 10000 lb 20000 lb
10 USD per 100 lb 9 USD per 100 lb 8 USD per 100 lb
SAP AG 2002
Pricing determines prices and surcharges/discounts (= conditions) for a business transaction and allows the user to specifically influence these conditions manually. Prices, surcharges, and discounts are stored in condition records. You can define conditions at any level. A level corresponds to the fields in the condition table in which a condition record is stored. The level also represents the key fields for access to a condition. Common levels at which price agreements are made are predefined in the standard system. You can add any levels that you need. You can make conditions dependent on any fields of a business document. By specifying a validity period, you can restrict a condition to a specific period. You can maintain the values within a condition record (price, surcharge, and discount) depending on a scale (weight-based, volume-based, or value-based scale). You can also use multi-dimensional scales. There is no limit to the number of scale levels. For each condition record, you can define a lower and an upper limit that allows you to manually change a pricing element within the limits specified.
(C) SAP AG
SCM612
29
3.29 Shipment Cost Settlement with DirectTransfer Shipment costs Item 1
576 Financial Accounting
Transfer
Requirements
Accruals in FI Assignment in CO A XX
B XX
Entr y/acceptance of services performed
Cost center 2556
Settlement with service agent
Accruals become payables B XX
1058 XX
Invoice / credit memo
SAP AG 2002
Shipment costs are settled with the service agent by shipment cost item. Settlement includes: Assigning and transferring shipment costs to Financial Accounting, the formation of accruals, and the assignment of costs to a CO object. Settlement of costs with the service agent: Posting payables by cancelling the accruals. You need to enter and accept the services provided before you can transfer costs to Financial Accounting. The system automatically creates the service entry sheet based on a purchase order for external services. Before you can settle costs with the service agent, you need to create an invoice using manual invoice verification or create a credit memo using the credit memo procedure.
(C) SAP AG
SCM612
30
3.30 Steps During Settlement
1. Account assignment • G/L account determination • Assignment for Controlling
2. Transfer to Financial Accounting • Purchase order determ ination • Creation of the service entry sheet • Establishment of accruals
3. Invoice creation • Credit memo procedure (ERS procedure) • Manual Invoice Verification
SAP AG 2002
During account assignment the system determines the correct G/L account in Financial Accounting for each shipment cost item and the assignment for Controlling. Account assignment can be carried out at different levels, depending on how detailed you want to track costs. Transfer to Financial Accounting to establish accruals requires the entry of services performed. However, each service entry sheet is based on a purchase order. You must initially create this purchase order for the service agent in Purchasing. During the posting process, services performed are accepted; to establish accruals, the system generates an accounting document in Financial Accounting. The system creates additional subsequent documents in Financial Accounting. Using the credit memo procedure, also referred to as the ERS (Evaluated Receipt Settlement) procedure, you can settle the shipment costs with the service agents without receiving invoices from them. You can choose from different settlement periods. Transfer the calculated shipment costs to Financial Accounting. The invoices are verified by the service agent. If the service agent discovers variances, you can post these as subsequent debits/credits. If you receive invoices from the service agent, you can also verify the invoices manually and create the invoices manually.
(C) SAP AG
SCM612
31
3.31 Settings Necessary for Integration: Topic Objectives
At the conclusion of thi s topic, you will be able to: Make the necessary customizing settings in
the R/3 System to interface the R/3 System transportation application with the APO TP/VS component. Create the necessary material master data in
the R/3 System for the APO TP/VS integration
SAP AG 2002
(C) SAP AG
SCM612
32
3.32 R/3 Customizing and Master Data Activities
Customizing A ctivities Transportation relevance of orders and deliveries Definition of Shipment Document Number Ranges Definition of Shipment Types Transportation Planning Point Determination
Material Master Requirements Check ATP-Category Create Packaging Materials needed in TP/VS Check Strategy Group
SAP AG 2002
(C) SAP AG
SCM612
33
3.33 Transportation Relevance R/3: Transportation relevance of deliveries
Route
Delivery Type
Item Category
SAP AG 2002
R/3 IMG: Logistics Execution Transportation Shipments Maintain Transportation Relevance Only transport-relevant deliveries can be assigned to shipments. Outbound deliveries route determination has to be maintained, because outbound deliveries without an assigned route are not transportation relevant. For inbound deliveries, relevance is determined from the Item Category and Delivery Document Type.
(C) SAP AG
SCM612
34
3.34 Shipment Document Number Ranges R/3 and APO: Definition of Number Ranges R/3 IMG:
Logistics Execution Transportation Shipments Define Number Ranges for Shipments
APO IMG:
Advanced Planner and Optim izer (APO) Transportation Planning/ Vehicle Scheduling (TP/VS) Basic Settings Define Number Range for Temporary Shipments
APO IMG: ... Define Number Range for Shipments
R/3
External number range in the R/3 System has to correspond w ith internal number range in APO.
APO
SAP AG 2002
(C) SAP AG
SCM612
35
3.35 Shipment Type Required Settings
R/3: Definition of Shipment Types Example for outbound shipments:
SAP AG 2002
IMG: Logistics Execution Transportation Shipments Define Shipment Types
Note: Maintain Do not adopt stages and No legs to be determined!
(C) SAP AG
SCM612
36
3.36 Transportation Planning Point R/3 : Transportation Planning Point Determination: IMG:
Enterprise Structure Definition Logistics Execution Maintain Transportation Planning Point
IMG:
Logistics Execution Transportation Interfaces Transportation Planning Point Determ ination
SAP AG 2002
Update the Transportation Planning Point determination table so that TP/VS can determine the Transportation Planning point to be assigned to the shipment documents created in TP/VS planning. A default transportation planning point should also be maintained. The Shipping Point and Shipping Type can be used in the table to determine the Transportation Planning Point.
(C) SAP AG
SCM612
37
3.37 Packaging Materials Needed for APO Mapping R/3 : Packaging Materials needed for APO Mapping Table for Vehicle s: SAP-Menu: Logistics Materials
Management Material Master Material Create (special) Packaging (Transaction: MM01)
APO
SAP AG 2002
Create materials of material type VERP (naming should be the same as that used in the APO Transport Methods). Note: In material master view Sales: General/Plant Data a packaging material type means of transport (For example, Trucks) has to be maintained. See Packaging Material Types in R/3 IMG: Logistics GeneralHandling Unit ManagementBasicsDefine Packaging Material Types
APO: Mapping Table for Vehicles IMG: Advanced Planner and Optimizer (APO) Transportation Planning/Vehicle Scheduling(TP/VS) Interfaces Maintain Mapping Table for Vehicles Note: The APO Mapping Table for Vehicles is key sensitive. Maintain the column for external vehicle description only by using uppercase.
(C) SAP AG
SCM612
38
3.38 Material Master Data Field Checks
SAP AG 2002
SAP-Menu: Logistics Materials Management Material Master Change Immediately
Material
ATP-Category in Material Master
View: MRP 3: See Availability Check field Checking Group for Availability Check: 02 (Individual rqmt) This field must be set for individual requirements for sales requirement data to be transferred to APO. Strategy Group There are four R/3 strategy groups that are not supported in APO: 11 – Gross requirements 59 – Phantom Assembly 52 – Future Use 62 – Future Use In addition, some strategy groups are configured so that requirements are not transferred to APO. If requirements are not transferred to APO, transportation planning will not occur for the material.
(C) SAP AG
SCM612
39
3.39 R/3 Transportation Processing Overview: Unit Summary
You are now able to: Explain the organizational units related to R/3 System transportation De scribe the structure of the shipment document and its functions Identify and locate important information in the shipment document De scribe the processe s related to R/3 System freight costing Explain the purpose, structure and processe s related to the shipment cost document Make the necessary setting to interface an R/3 System with an APO TP/VS system SAP AG 2002
(C) SAP AG
SCM612
40
3.40Exercises Unit: R/3 Transportation Processing Overview Topic: Transportation Planning Point At the conclusion of this exercise, you will be able to: •
Understand the organizational units relevant for transportation processing in Customizing.
•
Create a Transportation Planning Point to be used for shipment documents created by APO TP/VS planning.
As an employee in transportation planning and processing, you are also a member of the APO implementation team in the transportation area. Familiarize yourself with R/3 transportation processing in general before you begin setting up the system and trying out its shipment processes. You examine the structure of the shipment documents and identify what information they contain. Create two new shipment types to facilitate the creation of R/3 shipment documents from planned shipments in TP/VS. You also need to familiarize yourself with the organizational structures, to learn how they are defined and assigned. Create a new Transportation Planning Point to be used when creating R/3 shipment documents from the APO TP/VS component. 1-1
True or false? 1-1-1 A company code is an independent accounting unit. 1-1-2 Each plant has exactly one shipping point. 1-1-3 Shipments are processed at a transportation planning point. 1-1-4 Each transportation planning point must be assigned to a plant. 1-1-5 Each transportation planning point must be assigned to a warehouse number.
(C) SAP AG
SCM612
41
1-2
Which transportation planning points are defined for company code 1000? ____________________________________________________________ Go to the address screen for transportation planning point 1000. On which street is it located? ______________________________________________________
1-3
Create a new Transportation Planning Point to be used for shipments created from the APO TP/VS component. Identify the Transportation Planning Point as AP##. Assign it to Company Code 1000. Description: TP/VS Group ## In the Edit Address fields: Name:
APO TP/VS GR ##
Search Term: AP##
1-4
(C) SAP AG
Country:
DE
Language:
English
When shipment documents are created from the APO TP/VS system, the Transportation Planning Point must be determined for each shipment document. In this step you will update the interface table that is used to determine the Transportation Planning Point. Shipments will be planned for Shipping Point X0## Dresden. Create the following entries in the Determination of Transportation Planning Point table. Shipping Point
Shipping Type
X0##
Blank
X0##
01
TrspPlanPt AP##
AP##
SCM612
42
Exercises Unit: R/3 Transportation Processing Overview Topic: Shipment Document Type At the conclusion of this exercise, you will be able to: • Create shipment document types used for APO planning.
Shipment document types must exist for shipment documents created in APO TP/VS planning. You will create a shipment document type for inbound shipments created in TP/VS and a shipment document type for outbound shipment documents created in TP/VS planning. In addition, you will update the Transportation Planning point interface table for the R/3 System to APO TP/VS environment.
2-1 An outbound shipment for your group has been created in the system as an example. Display the outbound shipment. Search for the document using the F4 Help. Use the External ID 1 field as a search term. External ID 1: GR##-1. (Note: This search is case-sensitive; enter the External Identification EXACTLY as shown.) 2-1-1 Which outbound deliveries does this shipment contain? _____________________________________________________
(C) SAP AG
SCM612
43
2-1-2 Find the following information in the shipment document: Shipment type: _____________________________________________ Ship-to address: _____________________________________________ Shipping point: _____________________________________________ Shipment weight: _____________________________________________ 2-1-3 Display the corresponding document flow. What order initiated this document flow? What is its status? ______________________________________________________ 2-1-4 Check whether the shipment costs have already been calculated for this shipment. To do this, check the overall status of shipment cost calculation in the shipment header. Overall status of shipment cost calculation: ________________________________ Number of the shipment cost document: ________________________________ 2-2
To facilitate creation of inbound shipment documents in the R/3 System corresponding to planned inbound shipments in APO TP/VS, create a new shipment type, AI##, using existing Shipment Type 0010 as a template. In the new shipment type you need to make the following settings: Field Name
Data
Shipment Type Description
APO Inbound GR##
No. Range Ext.
02
Adopt Route
2-Do Not Adopt stages
Determine Legs
blank (No legs to be determined)
Weight Unit
KG (Kilograms)
Volume Unit
M3 (Cubic Meters)
Copy Routine
11 (Route/Deadlines)
Do not change any other settings.
(C) SAP AG
SCM612
44
2-3
To enable creation of outbound shipment documents in the R/3 System corresponding to planned outbound shipments in APO TP/VS, create a new shipment type, AO##, using existing Shipment Type 0002 as a template. In the new shipment type you need to make the following settings: Field Name
Data
Shipment Type Description
APO Outbound GR##
No. Range Ext.
02
Adopt Route
2-Do Not Adopt stages
Determine Legs
blank (No legs to be determined)
Weight Unit
KG (Kilograms)
Volume Unit
M3 (Cubic Meters)
Copy Routine
11 (Route/Deadlines)
Do not change any other settings.
(C) SAP AG
SCM612
45
Exercises Unit: R/3 Transportation Processing Overview Topic: Basics of Shipment Cost Processing At the conclusion of this exercise, you will be able to: •
Understand how the shipment cost document is organized and where it is found
•
Check whether shipment documents are relevant for shipment costs
•
Display shipment cost documents individually online
•
Search for information in the shipment cost document
In order to create a shipment cost document, the shipment document must be relevant for shipment costs.
3-1 First, answer the following questions about shipment cost processing: 3-1-1 What steps are involved in shipment cost processing? __________________________________________ __________________________________________ __________________________________________ __________________________________________ 3-1-2 Describe the structure of the shipment cost document: __________________________________________ __________________________________________ __________________________________________ 3-1-3 True or false? You can combine several shipment documents to form one shipment cost document. The shipment must have at least Shipment completed status before a shipment cost document can be created.
(C) SAP AG
SCM612
46
Exercises Unit: R/3 Transportation Processing Overview Topic: Shipment Costing and TP/VS-Related Customizing At the conclusion of this exercise, you will be able to: • Make the customizing settings necessary to assign your APO shipment types to a shipment cost type. • Make the relevant customizing settings necessary to perform shipment costing for shipments planned in APO TP/VS and provide the ability to perform carrier selection in TP/VS using freight rates established in the R/3 System. • Set up Pricing Procedure determination in Shipment Costing. The ability to perform shipment costing for both inbound and outbound shipments and to provide the ability to influence carrier selection based on actual freight rates are significant benefits of using the R/3 Transportation application combined with the APO TP/VS component. As a member of the TP/VS project team you will need to make the required customizing settings in the R/3 System to facilitate these functions. 4-1
Assign your two new Shipment Types AI## and AO## to Shipment Cost Type 0001 in R/3 Customizing. 4-1-1 Set the Shipment Header, Leg, Load Transfer Point and Border Crossing Cost Types as Relevant for shipment costs for each assignment.
4-2
Because you will be using tariff zone codes in your freight rates for shipment costing, you must update the tariff zone determination table to include your new Transportation Planning Point for each of your carriers. You have three carriers that have rates established for shipment costing and carrier determination in TP/VS: 1058, 1925 and 1930. These carriers are also used for shipments created for Transportation Planning Point 1000, so you can copy as the existing entries to your Transportation Planning Point AP##. You should also copy all subitems in the entry.
4-3
Update the shipment costing pricing procedure determination table to reflect your new Transportation Planning Point. Use Transportation Planning Point 1000 as a reference for the copy as process.
4-4
Make the required setting in the Purchasing Data determination table for your new Transportation Planning Point, AP##. Use the same purchasing organizational data as TransportationPlanning Point 1000.
(C) SAP AG
SCM612
47
4-5
To satisfy a requirement for TP/VS Carrier Selection when external costs are used as a criteria for selection, make an entry in the LES Shipping Point Determination table for your plants and their corresponding shipping points. The table entries are as follows: Shipping Condition
(C) SAP AG
Loading Group
SCM612
Plant
Shipping Point
10##
Z0##
12##
X0##
48
Exercises Unit: R/3 Transportation Processing Overview Topic: Stock Transport-Related Customizing At the conclusion of this exercise, you will be able to: • Make the required, basic customizing settings required for stock transport processing. When a new plants are established in the R/3 System, there are some fundamental settings required to facilitate the processing of stock transports both inter and intra-company. These settings are independent of TP/VS. You must make these settings before stock transport orders are created in the R/3 System. 5-1
To complete the required customizing settings, perform the following steps: 5-1-1 Copy the customer master record (1187) representing Plant 1000, to a new customer master record, T-S090##. You must copy all views (General, Company, and Sales Area) to your new customer master. 5-1-2 Copy the customer master record (22000) representing Plant 2200, to a new customer master record, T-S200##. You must copy all views (General, Company, and Sales Area) to your new customer master. 5-1-3 Update the Plant table in Stock Transport customizing with your new customer master for Plant 10##. Also, update the Plant table for Plant 22## with the customer account number you just created for the plant T-S200##. 5-1-4 Check and make any required assignments in the Assign delivery type/checking table in Stock Transport customizing. The following assignments must exist: Type: NB SPlt: 12## UB 10##
DlvTy: NLCC C: B NL RP
5-1-5 Check and make any required assignments in the Purchasing document type table in the Stock Transport customizing area. The table must include the following combinations of allowed stock transports and corresponding Purchase Order Document Types: 10## to 12## UB No one-step processing 12## to 22## NB No one-step processing 5-1-6 Verify and make any necessary changes to the Transportation Relevancy tables. In this step you will make sure that delivery document types NL and NLCC are set as relevant for transportation processing. In addition, you must verify that all relevant item categories for these document types are set as relevant for transportation processing. Unless these objects are set set as relevant for transportation processing you will not get shipment documents created when TP/VS planned shipments are published. (C) SAP AG
SCM612
49
Exercises Unit: R/3 Transportation Processing Overview Topic: Settings Necessary for Integration At the conclusion of this exercise, you will be able to: • Create the Packaging Materials needed for APO TP/VS planning and integration with the R/3 System. When APO TP/VS creates shipment documents and they are subsequently transferred to the R/3 System for execution, the Transportation Methods codes from TP/VS are translated into corresponding R/3 System packaging materials in the shipment document. These packaging materials must exist in the R/3 System Material Master. 6-1
Create two Material Master records, FTL-## and LTL-## by creating with reference’ from TRUCK-04 and TRUCK-05, respectively. These materials should have Material Type of VERP and Industry Sector of Mechanical Engineering. The following views should be created: Basic Data1, Sales: Sales Org. Data 1, Sales: Sales Org. Data 2, Sales: General/Plant Data and Accounting 1. In the Organizational Data enter only your Plant 12## but copy from Plant 1200 of the reference material. Description for FTL-##: FTL Group ## Description for LTL-##: LTL Group ## All other data fields should remain the same as the reference material.
(C) SAP AG
SCM612
50
3.41Solutions Unit: R/3 Transportation Processing Overview Topic: Transportation Planning Point 1-1
True or false? 1-1-1 True 1-1-2 False A plant can have more than one shipping point. 1-1-3 True 1-1-4 False A transportation planning point is only defined for a particular company code and is not linked to other organizational units. 1-1-5 False A transportation planning point is only defined for a particular company code and is not linked to other organizational units.
1-2
Transportation planning points for company code 1000: R/3 IMG: Enterprise Structure → Definition → Logistics Execution → Maintain Transportation Planning Point Company code 1000: Transportation planning points: 0007, 1000, 1010, 1011, 1200 Select the entry 1000: → Goto → Address Street/House number: Altersdorferstr. 13
1-3
To create the Transportation Planning Point: Select New Entries Enter the new Transportation Planning Point, the description, and the Company Code. Enter. Enter the Address data. Enter. Save.
1-4
Update the interface table used to determine the Transportation Planning Point in the APO system. R/3 IMG: Logistics Execution → Transportation → Interfaces → Transportation Planning Point Determination Select New entries. Make the entries as shown in the Exercise. Choose Save.
(C) SAP AG
SCM612
51
Solutions Unit: R/3 Transportation Processing Overview Topic: Shipment Document Type
2-1
Display the Inbound shipment document: Logistics → Logistics Execution → Transportation → Transportation Planning → Display Select the F4 key. Enter the search data in the External ID 1 field. Choose Execute. Choose your shipment from the shipment list. 2-1-1 Outbound deliveries: Shipments and deliveries overview screen: One outbound delivery is involved in this shipment. Number: Document numbers will vary 2-1-2 Information in the shipment document: Shipment type:
Shipment overview: Shipment type field:
_________________________________ Ship-to address: Shipments and deliveries overview screen: Recipient address field: _________________________________ Shipping point: Shipments and deliveries overview screen: Shipping point field: __________________________________ Shipment weight: Shipments and deliveries overview screen Total weight field: __________________________________
(C) SAP AG
SCM612
52
2-1-3 Document flow: Environment → Document flow Order number: Document numbers will vary The status of the order is completed. 2-1-4 Shipment costs:
→Goto→ Shipment overview: Shipment cst cal tab Overall status of shipment cost calculation: Completely processed Number of the shipment cost document: Choose Shipment cost document. Document numbers will vary 2-2
To create the inbound TP/VS Shipment Type: R/3 IMG: Logistics Execution → Transportation → Shipments → Define Shipment Types Select Shipment Type 0010. Choose Copy As. Enter Shipment Type AI## and the remainder of the settings from the exercise. Choose Enter. Choose Save.
2-3
To create the outbound TP/VS Shipment Type: R/3 IMG: Logistics Execution → Transportation → Shipments → Define Shipment Types Select Shipment Type 0002. Choose Copy As. Enter Shipment Type AO## and the remainder of the settings from the exercise. Choose Enter. Choose Save.
(C) SAP AG
SCM612
53
Solutions Unit: R/3 Transportation Processing Overview Topic: Basics of Shipment Cost processing 3-1
Questions about shipment cost processing: 3-1-1 Steps in shipment cost processing: Shipment cost processing begins with the creation of the shipment cost document. Within the document: - You calculate the shipment costs - Find the G/L accounts in FI and the CO objects (account assignment) - Transfer the shipment costs to FI and CO - Settle the shipment costs with the forwarding agents (invoice verification) You can automate most of these steps. 3-1-2 Structure of the shipment cost document: The shipment cost document consists of three levels: Header: Contains data that is relevant for the entire document, such as status and administrative data Items: This level establishes what costs were incurred for what purpose and with whom they should be settled Subitems: The actual calculation takes place at this level.The costs are calculated according to condition records defined in the system. 3-1-3 True or false? False. Only one shipment cost document is created per shipment document. (2) False. The required status can be set for each shipment cost type, but planned status at least is required.
(C) SAP AG
SCM612
54
Solutions Unit: R/3 Transportation Processing Overview Topic: Shipment Costing and TP/VS-Related Customizing 4-1
Assign your Shipment Types AI## and AO## to ShipmentCost Type 0001: R/3 IMG: Logistics Execution→Transportation→Shipment Costs→Shipment Cost Document→ Shipment Cost Relevance and Default for Shipment Cost Type Enter Shipment cost type 0001 for your Shipment types. Choose Save. 4-1-1 Under Dialog Structure, select: Define shipment cost relevance for shipment type For your shipment types, select the Header, Leg, Load Transfer Point, and Border Crossing boxes. Choose Save.
4-2
Make the updates to the Tariff zone assignment table: R/3 IMG: Logistics Execution → Transportation → Shipment Costs → Basic Shipping Functions → Define and assign tariff zones Under the Dialog Structure select the line: Define organizational key for tariff zone assigs Select the records in TPPt 1000 for Service Agents: 1058, 1925 and 1930. Select the Copy as button. Type your Transportation Planning Point, AP##, over the TPPt 1000 and select Enter. Select Copy all for the dialog boxes, and continue for the information boxes. After the three entries are copied, select Save. Exit back to the menu.
(C) SAP AG
SCM612
55
4-3
Update the shipment cost pricing procedure determination table: R/3 IMG: Logistics Execution → Transportation → Shipment Costs → Pricing → Pricing Control → Define And Assign Pricing Procedures → Define pricing procedure determination for shipment costs You will create the pricing procedure determination data for your Transportation Planning Point by copying the records from Transportation Planning Point 1000 to the clipboard, then “paste-ing” the records in your Transportation Planning Point, Select Transportation Planning Point 1000. Select the → Determine pricing procedure path under the Dialog Structure. After the table is displayed, press Cntl + Y (Mark). The cursor should turn into the “cross-hair” symbol. Place the cross-hair in the upper left-hand corner of the first record, drag the cursor across the first record and then at the end of the first record, at the vertical scroll bar, drag the cursor down the screen to the line below the last determination record (the line with ‘It.Det.Grp’ of 0006). Release the left mouse button and press Cntl + C to copy the block to the clipboard. Select Transportation Planning Point under the Dialog Structure to return to the list of Transportation Planning Points. Select your Transporation Planning Point from this table. Select the → Determine pricing procedure path under the Dialog Structure. Place the cursor in the It.Det.Grp. field on the first line of the table. Press Cntl + V to copy the clipboard to the records in your Transportation Planning Point. Select Save.
4-4
Make the required entry in the Purchasing Data determination table for your Transportation Planning Point: R/3 IMG: Logistics Execution → Transportation → Shipment Costs → Settlement → Assign Purchasing Data Use the same purchasing organizational data as that for Transportation Planning Point 1000 and Shipment Cost Type 0001 by using the Copy As function. Select the line with TPPt 1000 and SCTy 0001 and choose the Copy As button. Enter your TPPt. AP##. Select Enter. Select Save.
4-5
Update the Shipping Point determination Table with your Plants and Shipping Points. R/3 IMG: Logistics Execution → Shipping → Basic Shipping Functions → Shipping Point and Goods Receiving Point Determination → Assign Shipping Points Select the New Entries button. Make the entries in the table from the data in your exercise.
(C) SAP AG
SCM612
56
Choose Save.
(C) SAP AG
SCM612
57
Solutions Unit: R/3 Transportation Processing Overview Topic: Stock Transport-related customizing 5-1
Perform the following steps to customize the Stock Transport environment: 5-1-1 Create a new customer master to represent your plant 12## in outbound delivery documents of transfers of materials to the plant. R/3 Standard Menu: Logistics → Logistics Execution → Master Data → Partner → Customer → Create → Total Customer Account Group: 0001 – Sold-to Customer:
T-S090##
Company Code: Sales Area:
1000 1000/12/00
Reference: Customer: 1187 Company: 1000 Sales Area:
1000/12/00
General data: Name:
Plant 12##
Search term:
Plant 12##
Postal Code:
01069
City:
Dresden
Transportation Zone: D000000000 Language:
English
Control data tab: Trading partner:
1000
VAT Registration:
DE123456789
Choose Enter. Select Company code data button. Company data: No data entry required. Choose Enter. Select Sales area data button. Sales area data: Select the Shipping tab. (C) SAP AG
SCM612
58
Shipping Conditions: (50 + ##) Enter the sum of 50 plus your
group ##
Select the Billing document tab. Tax Classification:
0 – non-taxable
Choose Save. 5-1-2 Create a new customer master to represent your plant 22## in outbound delivery documents of transfers of materials to the plant. R/3 Standard Menu: Logistics → Logistics Execution → Master Data → Partner → Customer → Create → Total Customer Account Group: 0001 – Sold-to Customer:
T-S200##
Company Code: Sales Area:
1000 1000/12/00
Reference: Customer: 22000 Company: 1000 Sales Area:
1000/12/00
General data: Name:
Plant 22##
Search term:
Plant 22##
Postal Code:
75015
City:
Paris
Region:
75
Transportation Zone: F000010000 Language:
English
Control data tab: Trading partner:
2200
VAT Registration:
FR93341612695
Choose Enter. Select Company code data button. Company data: No data entry required. Choose Enter. Select Sales area data button. Sales area data: Select the Shipping tab. Shipping Conditions: (50 + ##) Enter the sum of 50 plus your
group ##
Select the Billing document tab. Tax Classification:
0 – non-taxable
Choose Save. (C) SAP AG
SCM612
59
5-1-3 Update the Plant table in Stock Transport customizing: R/3 IMG: Materials Management → Purchasing → Purchase Order → Set Up Stock Transport Order Select the Plant button. Select Plant 12##. Select the Details icon. Enter your customer: T-S090## in the Customer no. – plant field. Choose Save. Select Plant 22##. Select the Details icon. Enter your customer: T-S200## in the Customer no. – plant field. Choose Save. Exit back to the Stock Transport Order customizing list. 5-1-4 Check and update the Assign delivery type/checking table. Select the Assign delivery type/checking button. Check and update the table for document types: NB and UB for your plants 12## and 10## per the Exercise. Choose Save. Exit back to the Stock Transport Order customizing list. 5-1-5 Check and update the Purchasing document type table. Select the Purchasing document type button. Ensure that there are two entries in the table that match the Exercise data. Enter and Save, if necessary. 5-1-6 Check Transportation Relevancy for the Stock Transport document types and related Item Categories. R/3 Customizing: Logistics Execution → Transportation → Shipments → Maintain transportation relevance Select Maintain transportation relevance for delivery types. Verify that delivery types: NL and NLCC are "checked" for transportation relevance. Exit back to the Activity box. Select Maintain transportation relevance for delivery item types, Verify that Item Categories: ELN, NLC and NLN are "checked" for transportation relevance. Exit back to the IMG.
(C) SAP AG
SCM612
60
Solutions Unit: R/3 Transportation Processing Overview Topic: Settings Necessary for Integration 6-1
To create the Material Master records: SAP Menu: Logistics→ Materials Management → Material Master → Material → Create (Special) → Packaging Enter Material Number : FTL-## Enter Industry Sector: Mechanical Engineering Enter Copy From Material: TRUCK-04 Select Select Views. Select the views. Choose Continue. Enter your plant 12## in the Plant data field and enter 1200 in the Copy From Plant data field. Choose Continue. On the Basic data 1 screen, enter the description as indicated in the Exercise. Choose Enter on all remaining screens. Choose Save on the Accounting 1 screen. Enter Material Number : LTL-## Enter Industry Sector: Mechanical Engineering Enter Copy From Material: TRUCK-05 Select Select Views. Select the views. Choose Continue. Enter your plant 12## in the Plant data field and enter 1200 in the Copy From Plant data field. Choose Continue. On the Basic data 1 screen, enter the appropriate description. Choose Enter on all remaining screens. Choose Save on the Accounting 1 screen.
(C) SAP AG
SCM612
61
4 APO Overview
Contents: Introduction to supply chain planning Overview of APO Planning Components
SAP AG 2002
(C) SAP AG
SCM612
1
4.2 APO Overview: Unit Objectives
At the conclusion of thi s uni t, you will be able to: Explain the advantages of APO List the components of APO Understand the integration between the APO components
SAP AG 2002
(C) SAP AG
SCM612
2
4.3 APO Overview: Business Scenario
The electronics manufacturer is implementing a number of APO components. It i s important to understand the relationship between the components and the role that each will play in the corporate planning process.
SAP AG 2002
(C) SAP AG
SCM612
3
4.4 The Supply Chain: From Supplier to Consumer
Information flow
Transfer
Supplier
Transfer
Manufacturer
Transfer
Distribution
Transfer
Retail Outlet
Consumer
CASH FLOW
Supply Chain Optimization
Increase customer responsivene ss at least cost
SAP AG 2002
Supply Chain Management includes the management of materials, information, and financial flows in a network consisting of suppliers, manufacturers, distributors, and customers. The coordination and integration of these flows within and across companies are critical in effective Supply Chain Management. Why manage the supply chain? Lower sourcing costs of finished goods and raw materials Improve customer service Dramatically lower inventory levels Leverage all resources to bring substantial benefits to a company
(C) SAP AG
SCM612
4
4.5 Key Supply Chain Problems Postponement
Customers
Pull
Delivery time
Bullwhip Effect
Lead time
Plants
Push
DCs
Suppliers
SAP AG 2002
Supply Chain
The key supply chain problem is the delivery time of products to the customer must be considerably shorter than the production or the lead time. In order to realize this and guarantee a high delivery service, inventory and safety stock must be built up at component or finished product level in plants or distribution centers (DC). You use postponement strategies to define how far the sales order links with the supply chain; in other words, where the decoupling of make-to-stock production (push strategies) (MTS), and maketo-order production (pull strategies) (MTO), takes place. The bullwhip effect refers to an increase in variability of a (constant) demand pattern due to large fluctuations at the manufacturer or the supplier as we move along the supply chain, triggered by lot size creation. Implementing an Advanced Planning System (APS) does not solve supply chain problems. It is also important that company bosses are prepared to consider making organizational changes to their companies, or at least looking into the possible benefits.
(C) SAP AG
SCM612
5
4.6 SAP's Total Supply Chain Solution Strategic Application Level Customer Relationship Management (CRM)
R/3 Core Business Application Level •Finance
Integration Strategic Enterprise Management (SEM)
•Logistics
•Database structure •Interfaces •Development tools •Communication
•Materials Management
Client-Server
•HR
Core level
•Sales
•Production Planning
• ••
Flexibility
Non-R/3 System s
Supply Chain Solutions (APO)
liveCache Electroni c Commerce B2B
Scalability Business Information W arehouse (BW )
Open Systems
SAP AG 2002
Advantages of APO High performance using liveCache technology Global server: Integrates multiple OLTP systems Collaborative planning via the Internet Simultaneous material and finite capacity requirements planning Cross-plant optimization of the resource load Sequence and setup time optimization of orders Transportation optimization with route planning Evaluation and analysis of orders Seamless integration between the APO and R/3 Systems
(C) SAP AG
SCM612
6
4.7 Levels of Supply Chain Management Planning Strategy planning
planning)
Ext. proc. planning PP/DS
SAP AG 2002
Production planning PP/DS SNP
SNP
Production for example, PP
Outbound delivery for example, LES, MM, SD
Deliver y planning ATP, TP/VS
External procurement at customer
Customer
Aggregat ed sales and demand pl anning Demand Planning (DP) Supply Networ k Pl anning (SNP)
Operational detailed planning (operational
External procur ement for example, LES, MM
planning)
Suppl y Chain Design Network Design (ND)
Partner
Partner
Supply Chain Collaboration marketplace integration
Supplier
Tactical planning: strategy realization and infrastructure planning (plan infrastructure) Operational aggregated planning (tactical
Supply Chain Collaboration marketplace integration
Decision of direction for the compan y
Execution
In Supply Chain Management, there is a planning level and an execution level. Within the planning level APS systems are used (APS = Advanced Planning Systems) and at the execution level, ERP systems (ERP = Enterprise Resource Planning) are used. The planning level is divided into different levels depending on if the decisions are strategic, tactical or operational. The criteria for deciding what belongs to which planning level is not primarily the planning horizon but rather the scope of the planning. Each hierarchically superior level determines the ranges of the planning levels below it. Strategic level (strategy planning): Comparatively unstructured and simple planning tools such as portfolio techniques (product life cycle analysis, Boston Consulting Group portfolios, and McKinsey portfolios, for example) are used to make decisions about the direction of the company (such as product diversification strategies, quality strategies, and cost leadership). Tactical level (strategy realization and infrastructure planning): Decisions about direction are realized at this level when the company is restructured based on strategies. Tactical planning is decisive for operational planning and execution because it forms the planning environment within the company (planning personnel, IT systems for planning, implementation and setting parameters, and planning processes) as well as the part of the company that physically executes (such as factory planning, personnel planning, transportation planning, and logistically-relevant IT system for execution). This links the operational planning level and the execution level. Operational level (operational aggregated and detailed planning): Structured, recurring planning based on tactical realization decisions such as strategies for settling sales orders and pre-planning, which are not questioned again in operational planning. Operational planning is also long-term to bridge bottlenecks that will occur in the future, such as early planning for seasonal requirements or planning runs to determine components with longer replenishment times. Planning for the future is usually done objectively or based on time since planning data is uncertain. Aggregated planning also serves to redirect tactical planning if necessary (for example, additional shifts, additional capacity, and outline agreements with suppliers.) Detailed planning attempts to optimally use the logistic system within the limits set by tactical and aggregated planning and based on the most current data.
(C) SAP AG
SCM612
7
Execution level: Along with the development of the product (production, stock transfer, sorting, receipt, delivery), administrative activities are also performed at the execution level. These activities are supported by execution systems, for example, when papers for production (production orders) are printed.
(C) SAP AG
SCM612
8
4.8 APO Planning Components
Monitor
APO Product Map
Suppl y Chain Cockpit
Tactical
Networ k Design
Supply Net wor k Planning
Agg. Planning
Detailed Planning Purchasing
Production Planning & Detailed Scheduling
Scheduling
Sales
Distribution Transportation Planning Planning & & Deplo yment
Planning
Vehicle Scheduling
Global Avail able-to-Promise
BUY
MAKE
STORE
MOVE
SELL
SAP AG 2002
Supply Chain Cockpit: A graphic tool for evaluating and controlling the supply chain. Network Design: Strategic planning for analyzing, optimizing, and reorganizing the supply chain. Long-term sourcing, production, and distribution decisions are supported here. Demand Planning (DP): Aggregated and detailed demand planning with a variety of forecasting techniques based on aggregated sales figures. Supply Network Planning (SNP): Finite, cross-location, mid to long-term production and procurement planning with simultaneous material planning and capacity scheduling. Deployment is used to plan short-term replenishment. Production Planning/Detailed Scheduling (PP/DS): Finite, detailed production planning. PP/DS uses simultaneous material planning and capacity scheduling, and optimization techniques to generate feasible plans that are in the optimum sequence with the optimum setup times. Transportation Planning/Vehicle Scheduling (TP/VS): Optimizes use of transportation vehicles and selection of carriers. Generates deliveries and shipments. Global Available-to-Promise (ATP): Rules-based availability check that is integrated with production planning and product allocation.
(C) SAP AG
SCM612
9
4.9 Network Design
Strategic Supply Chain Planning
SAP AG 2002
Network Design is a component used specifically for strategic planning. Use this tool to make assignment decisions (relationships between individual locations and assignment of products to locations), as well as additional decisions regarding locations (location determination and location selection), taking account of demand and cost structures. Network Design can also be implemented for regular evaluation of the existing supply chain in order to discover any weaknesses and take any necessary measures. There are four methods available in Network Design for planning the supply chain network. These methods optimize either geographical distances or costs, in each case taking the demand structures into account.
(C) SAP AG
SCM612
10
4.10 APO Planning Sequence with R/3 Integration R/3 or non-SAP s ystem
APO
Flexible Planning
Dem and Planning (DP)
Dem and Planned ind.reqmts management Sales & Sales order Distribution (SD)
Planned ind.reqmts Consumption
Sales order Supply Network Planning (SNP) Prod. Plng & Det. Schedlng (PP/DS) Planned order Conversion Production order
Production Planning (PP) Release, Confir mations
Purchasing (MM)
Planned order Production order
Purchase requisition Purchase order
Purchase requisition Purchase order Stock transport requisition
Stock transport requisition Deploy Stock transport order -ment Transp. Plng & Veh. Schedlng (TP/VS) Planned delivery Delivery Planned shipment / Shipment
Logistics Execution System (LES) Delivery Transfer order Execution SAP AG 2002
In APO Demand Planning (DP), you base forecasts on aggregated historical data from the R/3 Systemor Business Information Warehouse (BW) system (such as sales quantities from past sales orders). You use the Administrator Workbench in APO to upload aggregated historical data from the R/3 System or BW System. In APO Demand Planning you generate planned independent requirements (release forecast to APO Demand Planning) that are used for make-to-stock planning. Sales orders and planned independent requirements form the starting point for Supply Network Planning (SNP), Production Planning/Detailed Scheduling (PP/DS) and TP/VS in APO. Existing storage location stock is also included in the planning. Sales orders are entered in the R/3 System (sales module) but the availability check (or ATP check-Available to Promise) is done in APO. In Supply Network Planning (SNP) you plan for the short- or mid-term horizon for the entire supply chain: you generate stock transport requisitions (for planning and stock transfer) between distribution centers and plants, and can also generate planned orders (for in-house production planning) and purchase requisitions (for external procurement planning) directly in the production plant for the longer term. Transaction data generated in APO (such as planned orders) is transferred to the R/3 System through the R/3 APO interface (CIF: Core Interface). As soon as planned orders and purchase requisitions get closer to the today-line, the stock planner or buyer can collectively convert planned orders into production orders and purchase requisitions into purchase orders. You use the APO Deployment/TLB (Transport Load Builder) to convert stock transport requisitions into stock transport orders. APO is a planning tool: Execution functions such as release, confirmation, material staging, or goods movement for production orders or purchase orders are performed in the R/3 System. Confirmation and other data is then transferred back to APO from the R/3 System. You create planned deliveries and shipments in Transportation Planning and Vehicle Scheduling (TP/VS). In APO, TP/VS different deliveries can also be grouped together into one shipment. It is then possible to
(C) SAP AG
SCM612
11
convert planned deliveries and planned shipments into real deliveries and shipments and transfer them to the R/3 System.
(C) SAP AG
SCM612
12
4.11 Functions of Demand Planning
Cross-company Demand Planning (Internet) Consi stent, detailed, and consolidated plans Statistical and causal forecasting technique s Retail outlet
Lifecycle planning Promotion planning
Suppliers
Production units
Distribution centers
SAP AG 2002
Demand Planning is a complex, powerful, and flexible tool that supports your company's demand planning process. User-specific planning layouts and interactive planning books not only allow you to include different departments, you can also use them to include other companies in the forecast creation process. With APO Demand Planning you can use statistical forecasting methods and advanced macro techniques to create forecasts from sales history based on many different causal factors, You can test predefined, and user-defined forecast models, and forecast results, and use a consensus-based approach to consolidate the demand plans of different departments. You can use forecast overrides and promotions to add marketing intelligence and management adjustments. The seamless integration with APO Supply Network Planning supports an efficient Sales and Operations Planning (S&OP) process.
(C) SAP AG
SCM612
13
4.12 Collaborative Planning in APO Collaboration with Suppliers
Collaboration with Customers
Manufacturer
Supplier
Product requirements Production dates Procurement Delivery dates
Customer
Dem and plans Promotions Stock levels Delivery dates
Supply Chain Optimization High efficiency, precise information and short lead times to improve delivery of service SAP AG 2002
The term collaborative planning refers to the process that makes it possible for different companies along the supply chain to access cross-company information over the Internet, with the common goal of identifying bottlenecks or date shifts as early as possible. Collaborative planning allows the company to exchange demand, procurement, and stock data with its partners. You can define your own exception messages (alerts) and integrate them into the general alert management. If exceptions occur during planning, mail or fax messages can be generated automatically. APO Collaborative Planning supports the CPFR standard.
(C) SAP AG
SCM612
14
4.13 Supply Network Planning (SNP)
Scre en Title
APO - Pro du ct ID
Supply Network Planning
Objec t
Tex t
Obj ect 1
Te xt 1
Des Gra igGrid n Titlep h
Obj ect 2
Te xt 2
Ke y Figure 1
Obj ect 3
Te xt 3
Ke y Figure 2
Obj ect 4
Te xt 4
Ke y Figure 3
To ta l
APO - Pro duct
To ta l
W 24
W 25
Cap acit y Lev elin g W 26
W 27
W 28
W 24
W 25
W 26
W 27
W 28
Ke y Figure 4 Se lec tion Profile
Ke y Figure 5
User Se le c tion ID
Grid 2 Title Ke y Figure 1 Ke y Figure 2 Ke y Figure 3 Ke y Figure 4 Ke y Figure 5
Plan nin g Book
SAP AG 2002
SNP Planning plans on a mid to long-term basis. It creates a rough quantity-based, cross-location production and distribution plan with individual rough bills of material (BOM) and routings. The SNP BOM contains critical products that are produced on bottleneck resources and products with a long replenishment lead time. SNP ensures that the right quantity is available on the right day without critical resources being overloaded. The smallest unit used for scheduling is days.
(C) SAP AG
SCM612
15
4.14 Supply Network Planning Scenario
Dem and Plan
Supplier
Plant
DC
Customer
SNP plans the material flow along the supply chain Mid to long-term, finite, cross-plant planning Prioritization of demands; supply optimization Re sult: Feasible plans SAP AG 2002
The role of Supply Network Planning includes: Planning supply to meet demand Integrating purchasing, production, and distribution in one consistent model in the entire supply network Synchronizing activities and planning material flow along the supply chain
(C) SAP AG
SCM612
16
4.15 Comparison of Mid- and Short-Term Planning
Sales orders
Forecasts
Sales orders
Production Planning/Detailed Scheduling
Forecasts
Supply Network Planning
●
PP/DS planned orders
●
SNP planned orders
●
Purchase requisitions
●
Purchase requisitions
●
Stock transfers
●
Stock transfers
●
PP/DS BOM and routing
●
SNP BOM and routing
●
Finite, detailed planning per location
●
Cross-plant finite planning
●
Sequences and setup times
●
Distribution and procurement
●
Continuous and order-related
●
Quantity and bucket-oriented
●
Pegging
●
No pegging
SAP AG 2002
Production horizon
Time
SNP integrates purchasing, manufacturing, distribution, and transportation so that comprehensive tactical planning and sourcing decisions can be simulated and implemented on the basis of a single, global consistent model. SNP uses advanced optimization techniques, based on constraints and penalties, to plan product flow along the supply chain. The result is optimal purchasing, production, and distribution decisions, reduced order fulfillment times and inventory levels, and improved customer service. Pegging is the link between receipts and issues along the supply chain. When an order is shifted, all dependent orders can be adjusted automatically.
(C) SAP AG
SCM612
17
4.16 Production Planning / Detailed Scheduling (PP/DS)
Production Planning/ Detailed Scheduling
SAP AG 2002
Supply Network Planning (SNP) is usually used for initial mid to long-term planning over the entire supply chain (in particular, when there are several plants and distribution centers). Production Planning and Detailed Scheduling (PP/DS) is usually used for to-the-minute, short-term planning in a production plant. In Supply Network Planning (SNP) demands are aggregated for a specified bucket (day for example). It is irrelevant whether a requirement falls within an early or a late shift, as requirements are only initially planned here. Planning does not include break times. The sequence of orders is not an SNP time consideration. Cross-plant planning, and mid- to long-term planning in the production plant do all play an important role in Supply Network Planning. Production Planning and Detailed Scheduling schedules orders to-the-minute (meaning that shifts and breaks are included here), and does include order sequences (sequencing and optimization of sequences). In the short-term, these functions are highly important for the production plant. As soon as a requirement (such as a sales order or planned independent requirement) falls within a specific horizon, it is no longer planned in the SNP planning run, but instead in the production planning run of PP/DS.
(C) SAP AG
SCM612
18
4.17 Functions of Production Planning/Detailed Scheduling (PP/DS) Plans production, external procurement, and stock transfer within the production plant to-theminute
Customer
Plans simultaneous material requirements and schedules finite capacity at operation level for the short-term Resource 2 Resource 1 Resource 3 30
Resource 3 20
Resource 2 Resource 1
10
Takes order sequences into account Optimizes machine schedules (sequences and lead times) Transfers the planning results to an execution system (such as the R/3 Shop Floor Control) Time
SAP AG 2002
Production Planning and Detailed Scheduling (PP/DS) is used mainly for short-term, to-theminute planning (both for in-house production and external procurement) in the production plant. PP/DS schedules and plans all operations of an order that are relevant for planning the different resources. PP/DS has the following functions: It generates planned orders (to plan in-house production), and purchase requisitions or scheduling agreement schedule lines (to plan external procurement) in the event of product shortage by using simultaneous material and capacity requirements planning to do this: You can define resources as finite resources (planning-critical resources) in the resource master. Order operations are only created at these resources if there is sufficient capacity for the order quantity on the corresponding date. When there is no available capacity, the system searches for a date on which the order operation can be carried out, taking account of the capacity situation. Takes order sequences into account: When new in-house production orders are created, the setup times in the new order can be determined automatically from the setup status of the resources (depending on the preceding order). It is possible to display the orders in graphic format (in the detailed scheduling planning board), and to sequence from there. You can use also the optimizer to execute a sequencing. Machine scheduling optimization: During planning, it is possible for orders to be generated that do not have an optimum order sequence. Therefore, you can change the sequence and resource assignments of existing orders using the optimization run. PP/DS is a planning tool. Execution functions such as confirmations and goods receipts are performed in the execution system (for example, the R/3 System). Therefore, the planning results are transferred to the execution system.
(C) SAP AG
SCM612
19
4.18 Deployment Deployment adjusts the stock transfers for short-term changes on both the supply and demand side (distribution detailed planning)
Fair Share
Proportional distribution
Proportional target fulfillment
Winnipeg
Quota arrangements
Push deployment
DC1
Calgary
Plant
Customer
DC2 Chicago
Push horizon
SAP AG 2002
The deployment function in SNP determines how and when inventory and planned supplies are deployed to distribution centers, customers, and vendor-managed inventory (VMI) accounts. It generates optimized replenishment plans that take into account short-term changes on the supply or demand side, as well as constraints, such as transportation and storage capabilities. A variety of deployment strategies are used depending on the current situation (for example, fair share, push deployment, and, pull-push deployment).
(C) SAP AG
SCM612
20
4.19 Global Available-to-Promise (Global ATP) Is it possible to deliver the product in the required quantity, and on the required date?
Event-driven Internet capabilities Rules-ba sed ATP:
Location substitution
Product substitution
Integration with PP/DS Rules
Product allocations High performance (time series)
SAP AG 2002
You use Global ATP (Available To Promise) to check product availability and capacities, to provide customers with reliable confirmation dates for their sales orders. ATP checks are triggered from the OLTP system (R/3 System, or non-SAP system) as an event (event-driven). In the interface with APO you can specify that the ATP check is to be done in APO and not the R/3 System. For example, if you create a sales order in the R/3 System, the system first checks if there is enough of the requested product in stock. The system can also check if receipts (for example, production orders and planned orders) have already been planned by the requested date. Global ATP has the following functions: Rules-based ATP: When there is no stock available, it is possible in APO to set it so that the system does an ATP check for the product at another location or else substitutes an alernative product for (location and product substitution). Integration with PP/DS: You can set Global ATP so that when a product is not available, the sales order directly triggers production. If it triggers an order for in-house production, APO creates a planned order for the required quantity in PP/DS. Product allocations: Product allocation allows you to manage the supply of scarce products to customers, so that each customer only receives an allocated amount. Time series: Planned orders and production orders are aggregated and represented in a time series, which can be used to evaluate the incoming requests from the sales orders. This improves performance of the ATP check.
(C) SAP AG
SCM612
21
4.20 Transportation Management: Planning Solution
APO
Transportation Planning Vehicle Scheduling
Long or mid-term bucket oriented planning. Use DP/SNP to determine aggregate transportation requirements. Short-term order-based planning using TPVS to consolidate/route transportation requirements
BW (Monitoring)
LES (Execution)
SAP AG 2002
The TP/VS component has the following functions: Transportation planning and transportation consolidation Vehicle scheduling and route determination in a dynamic environment Transportation mode and carrier selection Multi-pick up and multi-drop functions Management by exception The APO system includes the tactical and operational planning area from the SAP Transportation Management solution, which is complemented for transportation execution by the R/3 System component from the Logistics Execution System (LES). Transportation Business Content is available in BW 2.0B Connection to the R/3 System from Release 4.0B and higher. BW provides a dynamic monitoring and reporting tool for the TP/VS environment.
(C) SAP AG
SCM612
22
4.21 APO Planning Process
Dem and Planning
Supply Network Planning
Unconstrained Aggregat e Planning
Forecast Forecast
Planned Planned Prod Prod Orders Orders
Constrained
Stock Stock Transfer Transfer Orders Orders
Mid-term Sourcing/Repl en.
Deployment/Transport Load Builder Production Planning Detailed Scheduling
Constrained Detailed Planning
Transportation Planning / Deployment
Planned Planned Delivery Delivery Items Items Planned Planned Shipments Shipments
Constrained
Vehicle Scheduling
Load Consolidation Deliver y Schedul ing
SAP AG 2002
Supply Network Planning is used for long-term to mid-term planning. A major advantage of this component is the Sourcing function, which allows you to specify at which location which product is procured and how it is to be procured. Sourcing is optimized using functions such as Deployment and the Transport Load Builder (TLB). Bucket capacities, which show the most detailed level for day planning, are used for product planning in Supply Network Planning Vehicle Scheduling (VS) is a component for short-term planning. You can define planning horizons for both Supply Network Planning and Vehicle Scheduling. These horizons are independent of each other and must be planned separately. In Vehicle Scheduling, the resources and transportation processes are maintained in detail to allow for very exact planning. When the orders from Supply Network Planning are converted to VS orders, the following occurs: • The orders are put in a certain order. • The exact move time is determined. • Information and operations still required are added (data and operations that are not required for Supply Network Planning but are necessary for Vehicle Scheduling, such as loading activities).
(C) SAP AG
SCM612
23
4.22 Differences Between TLB and TP/VS
Transport Load Builder (SNP) Provides a Preliminary Transportation Plan for Supply Network Planning (or may serve as the tool of choice for plant/DC replenishment legs)
Consolidates Loads for Single Transportation Leg (creating a single delivery/shipment between two locations)
Vehicle Scheduling (TP/VS) Provides a Detailed Transportation Schedule for Inbound and Outbound Shipments (and/or replenishment) Consolidates Loads for Multiple Transportation Legs (creating an optimum delivery schedule for multi drops/pickups)
SAP AG 2002
(C) SAP AG
SCM612
24
4.23 Optimization Solutions
APO optimization solutions A complete range of optimization solutions adjusted to the planning tasks Linear programming/ m ixed/whole number programming
Local search + Constraint programming
Supply Network Design + Planning
Genetic algorithm constraint-based programming
Production Planning/ Detailed Scheduling
Transportation planning
SAP AG 2002
The following optimizers are available in APO: Optimizer for CTM, optimizer for PP/DS, optimizer for Network Design, optimizer for Sequence Planning, optimizer for Supply Network Planning, and optimizer for Transportation Planning. In Supply Network Planning, optimization problems usually can be solved with an exact mathematical solution procedure (which can be solved using linear equations). For this reason, linear programming is used for optimization in Supply Network Planning. Linear programming is able to calculate an exact solution. In Production Planning and Detailed Scheduling (PP/DS) however, there are usually more complex optimization problems for which no exact solutions can be found. Therefore, linear programming is less suited for PP/DS. Instead, solutions approximate an optimum or exact solution. Approximate optimization procedures are therefore more suited to be used in PP/DS (genetic algorithm/constraint-based programming). This allows the optimization system to find a suitable solution faster. The different optimizers can be installed on the same server on which the APO application, the liveCache, and the database are all installed (but you can also install them on different servers). The APO application server and the optimizer are linked via a TCP/IP connection. Here you specify whether the optimizer is to be called on the APO application server or on a different server (transaction sm59).
(C) SAP AG
SCM612
25
4.24 APO Overview: Unit Summary
You are now able to: Explain the advantages of APO List the components of APO Understand the integration between the APO components
SAP AG 2002
(C) SAP AG
SCM612
26
4.25Exercises Unit: APO Overview Topic: Overview of APO Components At the conclusion of this exercise, you will be able to: •
List the components of the Adavanced Planner and Organizer.
•
Describe the basic function of each component.
•
Understand the integration between the components.
The Advanced Planner and Optimizer product includes a number of planning tools that can be used to plan various enterprise functions such as production, plant stocks, and transportation. One of its most powerful features is the integration between the components, which such that it can provides a total supply chain optimization solution. As a member of the TP/VS project team, it is important for you to understand the relationship between various components and the transportation planning function. 1-1
Within supply chain management, there is a planning level and an execution level. APO provides components at the _______________ level and the R/3 System provides ERP for the ________________________ level.
1-2
There are three levels of planning . They are: 1) _________________________________________ 2) _________________________________________ 3) _________________________________________
1-3
The APO components PP/DS and TP/VS are examples of components used for ________________________________ planning.
1-4
Network Design (ND) is an example of _________________________ planning.
1-5
True or False: Supply Network Planning (SNP) is usually used for short- term planning over the entire supply chain. 1.6 Which of the following are not components of APO: a) Material Requirements Planning (MRP) b) Demand Planning (DP) c) Supply Network Planning (SNP) d) Task and Resource Management (TRM)
(C) SAP AG
SCM612
27
e) Production Planning/Detailed Scheduling (PP/DS) f) Transportation Planning / Vehicle Scheduling (TP/VS) g) Global Available-to-Promise (GATP) 1-7
True or False: Planned independent requirements from Demand Planning are one of the inputs to Supply Network Planning.
1-8
True or False: Sales orders and planned independent requirements are input to Production Planning/Detailed Scheduling. 1.9
The term ____________________________________________
refers to the process that makes it possible for different companies along the supply chain to all access cross-company information over the internet. 1-10
A major difference between planning by the Transport Load Builder (TLB) and Vehicle Scheduling (VS) is that TLB consolidates loads for a _________________ transportation leg, whereas VS provides load consolidation for _______________________ legs.
1-11
The TP/VS component of APO uses the optimization technique called ___________________________________________.
(C) SAP AG
SCM612
28
4.26Solutions Unit: APO Overview Topic: Overview of APO Components 1-1
Within supply chain management, there is a planning level and an execution level. APO provides components at the planning level and the R/3 System provides ERP for the execution level.
1-2
There are three levels of planning . They are: Strategic Tactical Operational
1-3
The APO components PP/DS and TP/VS are examples of components used for short-term planning.
1-4
Network Design (ND) is an example of strategic planning.
1-5
True or False. Supply Network Planning (SNP) is usually used for mid- to longterm planning over the entire supply chain. 1.6
Which of the following are not components of APO:
Material Requirements Planning (MRP) Task and Resource Management (TRM) 1-7
True or False. Planned independent requirements from Demand Planning are one of the inputs to Supply Network Planning.
1-8
True or False. Sales orders and planned independent requirements are input to Production Planning/Detailed Scheduling.
1-9
The term collaborative planning refers to the process that makes it possible for different companies along the supply chain to all access cross-company information over the internet.
1-10
A major difference between planning by the Transport Load Builder (TLB) and Vehicle Scheduling (VS) is that TLB consolidates loads for a single transportation leg, whereas VS provides load consolidation for multiple legs.
1-11
The TP/VS component of APO uses the optimization technique called tabular search.
(C) SAP AG
SCM612
29
5 APO Integration and Master Data
Contents: APO Integration Core Interface RFC Links Master Data Objects Integration Models Transfer of Master Data
SAP AG 2002
(C) SAP AG
SCM612
1
5.2 APO Integration and Master Data:Objectives
At the conclusion of thi s uni t, you will be able to: Understand the RFC links between the APO and the R/3 Systems and the R/3 System and the APO System Name the APO master data objects De scribe the concept of initial and incremental data transfer of master data from an R/3 System into an APO System Create an integration model for the transfer of master data in a APO TP/VS environment Transfer master data
SAP AG 2002
(C) SAP AG
SCM612
2
5.3 APO Integration and Master Data: Business Scenario
The PC manufacturer use s the R/3 System as an execution system and APO for planning. The Core Interface (CIF) provide s a close integration of the systems. Information can be exchanged in realtime, including both master and transaction data. To use the APO system as a planning system, the PC manufacturer must transfer key master data to the APO environment using the CIF. Establi sh various methods to provide for the initial data transfer and ongoing updates of ma ster data.
SAP AG 2002
(C) SAP AG
SCM612
3
5.4 APO Integration: Topic Objectives
At the conclusion of thi s topic, you will be able to: De scribe the RFC link between APO and the
R/3 System(s) in an APO – R/3 landscape De scribe the APO Core Interface De scribe the R/3 Plug-in technology
SAP AG 2002
(C) SAP AG
SCM612
4
5.5 APO Integration (1)
R/3 -> APO
APO -> R/3
Master data
Transaction data
Plants, vendors, customers Materials Work centers (capacities) Routings and bills of material ...
Sales orders Planned/production orders Purchase orders Supplies ...
Planning results Manufacturing orders Order proposals Result of availability check ...
APO R/3 4.6C
R/3 4.6C
BW SAP AG 2002
As a rule, the SAP-APO System is used in connection with other components of the SAP System or with non-SAP Systems. There are two different integration concepts: Linkage with non-R/3 Systems: The required interfaces are implemented as Business Application Programming Interfaces (BAPIs). Linkage with R/3 Systems (one or more): The required interface is marked as an APO Core Interface (CIF). A mutual system connection has been set up in Customizing to enable the system to transfer data relevant for the planning processes, from the execution R/3 System into APO, and also to return the planning results from APO into the R/3. The main tasks of the APO Core Interface include: Determining the source and target system in complex system environments Providing the SAP-APO System with the relevant master and transaction data Transferring data changes (transaction data) Returning planning results to the execution system (R/3 or external system). TP/VS was introduced in Release 3.0A of APO and is intended for use in R/3 System Releases 4.6C and higher. It's also possible to integrate TP/VS by using Release 4.6B and Plug-in 2001.1 or higher, by contacting development.
(C) SAP AG
SCM612
5
5.6 APO Integration (2)
SAP R/3 Non NonR/3 R/3System System
LO
SD SD HR
BAPI
CIF
BAPI
(Core Interface)
SAP APO
BAPI s
BAPI
SAP AG 2002
The APO Core Interface (CIF) is responsible for the data exchange between the APO and R/3 Systems. The APO CIF is a real-time interface that links APO with one or several R/3 Systems.
The system only transfers the data objects needed in the data structures in APO for the different planning and optimization processes, from the complex dataset of the R/3 into APO.
The APO Core Interface guarantees both the initial data transfer (initial transfer) and the data changes (transfer of data changes) within APO.
The outbound delivery from APO CIF takes place as an R/3 Plug-in.
The integration of R/3 with the CIF is possible as of release 3.1I. Earlier releases or an R/2 System can be connected with BAPIs as Non-R/3 Systems.
TP/VS was introduced in Release 3.0A of APO and is intended for use in R/3 Releases 4.6C and higher. You need Plug-in 2000.2 or higher. It's also possible to integrate TP/VS by using Release 4.6B and Plug-in 2001.1 or higher, by contacting development.
(C) SAP AG
SCM612
6
5.7 APO Integration (3)
R/3 Sales order Planned order Production order Purchase order Delivery Shipment ... Plant, customer,... Material master Capacity Rout ing and bill of material
APO
CIF Real-time CIF
Order
live live Cache Cache
• Production • Procurem ent • Replenishm ent
Location Product Resource Production process model
SAP AG 2002
The planning in APO is based on its own master data, which is usually transferred automatically from a R/3 System, but can also be created manually. The transfer of master data from the R/3 System is represented in the corresponding master data in APO. Only the master data relevant for planning in APO is transferred (firstly in the form of an initial transfer, and then later as a transfer of data changes). The R/3 System remains the execution system for the master data. You can only maintain the settings that the system cannot transfer from the R/3 directly into APO. The system transfers the transaction data relevant for planning, such as warehouse stock and sales or purchase orders, from the R/3 into APO via the CIF interface. And vice versa, the results of the planning in APO are returned to the R/3 via CIF and then performed there. This integration of transaction data generally takes place in real-time.
(C) SAP AG
SCM612
7
5.8 R/3 Plug-In Technology CIF
APO
R/3 Plug-in
CRM BW
R/3
BBP SEM
Information on R/3 Plug-in: SAPNet/R3-Plug-in SAP AG 2002
An R/3 interface is marked with an R/3 Plug-in, to enable the system to integrate a mySAP component (for example, APO or BW) with one or more R/3 Systems. With R/3 Plug-ins, several mySAP components can be inserted at the same time. Most Plug-ins concern Add-Ons (R/3 standard software enhancements with additional functions).
Plug-ins supply the components with transaction and master data. In this way, the CIF interface does not only provide the APO System with initial data records (initial supply), it also guarantees a stepby-step supply with all the relevant data changes. The system only transfers the object data relevant for the individual planning and optimization process in APO, from the complex data records into R/3. The integration between R/3 and APO is possible as of Release 3.1I. For TP/VS, it is possible as of Release 4.6C and restricted as of release 4.6B.
For easy integration from R/3 and APO, it is necessary to install a Plug-In relevant to the R/3 release. Support packages are also delivered for the Plug ins.
(C) SAP AG
SCM612
8
5.9 RFC: Link Between R/3 and APO
R/3
APO
Master/ Master/ transaction transaction data data
Core Core Interface Interface (selection (selection and and extraction extraction of of data) data)
Rem ote Function Call (RFC)
APO APO ma master/ ster/ transaction transaction data data live live Cache Cache
SAP AG 2002
A RFC (Remote Function Call) connection connects an SAP R/3 System and an APO System. The system transfers the data that is selected with the Core Interface (CIF) via this connection. To avoid confusion, an example of a data transfer from the R/3 into the APO System is shown on the diagram. The transfer of transaction data from APO to the R/3 System also takes place with RFC technology. The R/3 is a database-orientated system that stores the data in the database. The APO System, on the other hand, is available next to the classic database via the LiveCache (main memory orientated).
(C) SAP AG
SCM612
9
5.10 Structure of a RFC Link: Overview
Between an R/3 and an APO System 1. Naming logical system s Names for R/3 and APO exist in the R/3 Names for R/3 and APO exist in APO
2. Assign logical system s to clients The logical R/3 System is assigned to R/3 clients The logical APO System is assigned to APO clients
3. Define RFC destinations Target host for the logical R/3 System is known Target host for the logical APO System is known
4. Establish target system s The APO target system is known in R/3
5. Specify APO release The release of the APO target system is known SAP AG 2002
A RFC connection sets up communication between an R/3 System and an APO System. The system defines logical system names. In R/3 and APO, a logical system is named for both the R/3 and the APO Systems. The system assigns logical systems to the R/3 and APO clients. The system determines the actual RFC destination by specifying a physical connection for the logical system. The RFC destination also contains the logon data for the relevant system. The system defines the APO target destination from the view of the R/3 System, and vice versa. There is an obvious connection between both systems. Enter the release of the APO System in step five.
(C) SAP AG
SCM612
10
5.11 APO Integration with Non-R/3 Systems
SAP R/3 Non NonR/3 R/3System System
LO
SD SD HR
BAPI
CIF
BAPI
(Core Interface)
SAP APO
BAPI s
BAPI
SAP AG 2002
The data exchange between APO and non-R/3 Systems takes place via BAPIs.
BAPIs are documented standard interfaces that provide object-orientated access to SAP Systems (via C++, Java, Visual Basic, IDOCs, COM/DCOM, DelphiConnect, and so on).
(C) SAP AG
SCM612
11
5.12 APO Master Data: Topic Objectives
At the conclusion of thi s topic, you will be able to: Name the APO master data objects De scribe the concept of initial and incremental data transfer of master data from an R/3 System into an APO System Create an integration model for the transfer of master data in a APO TP/VS environment Transfer master data
SAP AG 2002
(C) SAP AG
SCM612
12
5.13 Master Data Objects of the CIF Initial transfer
R/3
APO
R/3 master data
APO master data
Plant
Location
Customer
Product
Vendor
Resource
Material master Transportation Zones
Transportation Zones
Incremental data transfer SAP AG 2002
The APO Core Interface concerns a real-time interface. The system only transfers the data objects from the complex dataset in R/3 into APO, that are needed in the data structures of APO. These objects have been determined to be required for the respective planning and optimization processes.
Both the initial data transfer (initial transfer) and the data changes (transfer of data changes) within APO take place using the APO Core Interface.
The master data objects in APO are not the same as those in the R/3 System. For the master data transfer it is the relevant R/3 master data that is displayed in the corresponding planning master data in APO.
The R/3 System remains the source system for the master data. Maintain directly in APO the specific APO master data that does not exist in the R/3 System.
(C) SAP AG
SCM612
13
5.14 Initial Data Transfer of Master Data: Overview
1. Generate integration model
Name Target system
Determine name and APO target system
Plant Material master Resource
Select master data
...
2. Activate integration model Integration model is active Start
Master data will be transferred
SAP AG 2002
Define the integration model that controls the transfer of master and transaction data in the R/3 System. You can find the menu option Core Interface Advanced Planner and Optimizer (the CIF menu) under Logistics → Central Functions → Supply Chain Planning Interface.
The integration model distinguishes between master data and transaction data. Select the two types of data in separate integration models and then transfer them separately.
In the integration model, select the dataset (master or transaction data) that you want to transfer. Specify the following in the integration model: • The APO target system for the data transfer • The data objects you want to transfer
You can delete integration models that you no longer need. You must first deactivate these integration models.
(C) SAP AG
SCM612
14
5.15 Generate Integration Model for Initial Data Transfer Name + application = unique definition of integration model Name
PC
Target sys.
APOCLNT800
Application
MD
APO System
Material m aster Customers
Vendors
Plants
Work centers
Selection of master data types
Production process models
...
Relevant m aterials
Material Plant
Selection criteria for the master data
1000
MRP type
...
Execute
+
Save
SAP AG 2002
The master data that the system will transfer for the first time (initial transfer), from the R/3 System into the APO System, is defined in an integration model. The R/3 System generates this integration model (transaction CFM1). An integration model is uniquely defined by its name and application. It is useful to create several integration models with the same name but as different applications. Ensure that the data pools of your integration models are generally not too big. This enables you to handle errors more easily. The target system that you specify in the integration model determines the APO System that the master data is transferred into. The target system is a logical (APO) system that must have a RFC connection. Use a particular integration model to specify which master data you want the system to transfer. First specify the master data types that flow into the integration model. In the second step, you specify the selection criteria to be used for the selection of the individual master data documents in the R/3 System. You complete the generation of the integration model by executing the model (this means that the data objects of the model are compiled) and then you save it.
(C) SAP AG
SCM612
15
5.16 Activate Integration Model for Initial Data Transfer
R/3
Integration model PC
Name
Target system APOCLNT800 Application
MD Active/Inact.
"Activate" PC
Material m aster AA Material Materialmmaster aster B Material m aster A
APOCLNT800 MD
10:00:00
Start
APO
Master data in APO
Material m A Material master aster Product B A Product A
SAP AG 2002
To transfer data into APO, you must activate an integration model that has previously been generated. You activate an integration model with the transaction Activate integration model (transaction code CFM2) in the CIF. You can have several integration models active at a time. Choose the Start function to trigger the data transfer into APO. The master data, or the equivalent of the R/3 master data will exist in the APO System when the run completes.
(C) SAP AG
SCM612
16
5.17 Transfer New APO-Relevant Master Data (1)
R/3
Name
New
Material m aster Q
X0
PC
Target sys. APOCLNT800 Application MD
Existing integration model Execute
Material m aster
...
Active/Inact.
PC
APOCLNT800 MD
11:00:00
PC
APOCLNT800 MD
10:00:00
Start
APO
New master data in APO
Save
"Activate"
X0
MRP type
+
Difference i s transferred
Product Q
SAP AG 2002
New APO-relevant master data (in the example on the slide above, a new material with MRP type X0), that corresponds with the selection criteria of an existing integration model (in the example, materials with the MRP type X0 are selected in the integration model), can be transferred into APO. The system regenerates the existing model (the new master data is also selected here) and then activates it. Two models with the same name are then active, the only differences being the dates and times. If the data transfer starts in this situation, the system simply transfers the difference data. The system compares the existing, active integration models with the new model. After the data transfer, the system deactivates the old integration model, leaving the new complete integration model as the active model. If you want the system to retransfer all the master data of an existing integration model, you must deactivate the old models and activate only the new one. A comparison of all active models then takes place. As in this case, the model with the old time is not active, all data is transferred again. If you have activated model one with the material masters A and B, and activate a model two in the second step with material masters B and C, then when you activate model two, only material C will be transferred. Then when you deactivate model one, the integration for material B remains. To ensure that the system has transferred all the APO-relevant master data, periodically regenerate and activate the existing integration models.
(C) SAP AG
SCM612
17
5.18 Transfer New APO-Relevant Master Data (2)
Execute integration model periodically Generate integration model Name
Target system APOCLNT800 Application
...
JOB_1
PC
MD
Variant PC_MAT
Execute
+
Step 1
Save
RIMODGEN report
Alternative:
JOB_1_AND_2 Activate integration model Name
PC
Target system APOCLNT800 Application
MD
JOB_2 Variant PC_MAT
Active/Inact.
+
Step 2
Start
RIMODAC2 report SAP AG 2002
Defining jobs enables the system to regenerate and then activate the integration models in regular intervals, as the R/3 System is constantly creating new APO-relevant master data. The system generates an integration model with the RIMODGEN report. You schedule this report by entering a variant (that you must have defined previously) as a job. The system activates an integration model via the RIMODAC2 report. You need a variant for this report too, in order to schedule it in a job. Executing an integration model consists of the generation and activation of an integration model. You can schedule these two steps with a job, where you define the two activities as two consecutive steps. For this procedure, you also need the relevant variants for both steps.
(C) SAP AG
SCM612
18
5.19 Incremental Data Transfer of Master Data (1)
Changes to APO-relevant master data are transferred. What is APO-relevant master data? Name
PC
Applicat. MD Material m aster
...
Relevant m aterials Material Plant
1000
MRP type
X0
...
Material A Material B Material C
...
Materials (generally: Master data) are APO-relevant
Integration model active PC
APOCLNT800
MD
SAP AG 2002
Any changes you make to the master data in the R/3 System that are also APO-relevant must be transferred into the APO System. The system does not usually carry out a new initial data transfer, but just transfers the individual changes to the master data. In the same way, the system also transfers a deletion flag for a material into APO. An incremental data transfer assumes that an active integration model is available for the relevant materials, and that the materials are APO-relevant. With the transfer of master data changes, remember that the system will transfer the complete data record. For example, if you change a field in the material master, the entire material master will be retransferred within the incremental data transfer.
(C) SAP AG
SCM612
19
5.20 Incremental Data Transfer of Master Data (2) Master data change
Change pointer generally active? Relevant message type active?
Material master A
Change pointer
Matls. planning MRP type
X0
Plan.del.time 10 days
Customizing
Mat B in-house pr.time Mat A plan.deliv.time ...
11 days
Variant DELTA_MD
Incremental data transfer Target sys. APOCLNT800 Object types Material m aster
APO
...
Changed master data in APO
Incremental data transfer Execute
Product A Plan.del.time 11 days
SAP AG 2002
The R/3 System is the dominant master data system. As a rule, the system performs changes to the master data in the R/3 System and transfers them from there into the APO System. With master data changes, it is not necessary for the system to totally retransfer all the master data as an initial data transfer. Instead, the system can transfer just the changed master data. For an incremental data transfer, set in Customizing ALE change pointers that are written for master data changes. First, you activate the change pointers (Activate change pointer in Customizing in ALE, transaction BD61), before you determine (in Customizing, Change pointer per message type, transaction BD50) which master data objects should have change pointers. (CIFMAT message type for material masters, CIFVEN for vendors, CIFCUS for customers, and CIFSRC for info records) If you use transaction CFC5, the settings for the message types CIFMAT, CIFVEN, and CIFCUS are automatically set. The process of incremental data transfer reverts to the ALE change pointer. This change pointer selects the master data for the system to retransfer. When you call up the transaction Incremental data transfer of master data (CFP1), specify the the logical target systems and the master data objects (material masters, vendors, sources of supply, and customers), that have changes to be transferred. You can save your settings for the incremental data transfer as variants, and, if necessary, use these variants for the periodic scheduling of incremental data transfer as a job (RCPTRAN4 report).
(C) SAP AG
SCM612
20
5.21 Real-Time Transfer of Master Data Changes Configuration procedure for transfer of master data changes
APO
Transaction CFC5 Material master Business Transaction Event, immed. ALE change pointer, periodic No incremental data transfer
Changed R/3 System master data objects are transferred into APO w hen the changes are saved in real-time
Customers Business Transaction Event, immed. ALE change pointer, periodic No incremental data transfer Vendors
Changes to R/3 System master data objects are recorded and the transfer of the changes is (periodically, for example) triggered
Business Transaction Event, immed. ALE change pointer, periodic No incremental data transfer SAP AG 2002
The system can transfer changes to APO-relevant master data (data contained in an active integration model) the material master, customer, and vendor in real-time (directly when updating a data change in the R/3 System) into the APO System. Access the settings for this function with transaction CFC5. In real-time transfer, the system transfers the complete data record that has been changed directly to the APO System (for numerous changes there are corresponding repercussions on the system performance). In the periodic transfer, the system collects and transfers the master data changes into the APO System, within a normal incremental data transfer. The incremental data transfer can finally be deactivated. You can control the incremental data transfer of master data with transaction CFC5. If the incremental data transfer is set to Business Transaction Event, immediately, the processing takes place without using change pointers. If the incremental data transfer is set periodically, the change pointers are automatically activated.
(C) SAP AG
SCM612
21
5.22 Transfer Master Data Changes Periodically
Evaluate and send change recordings Target sys. APOCLNT800 Object types Material m aster Customers
...
Schedule periodically
Variant DELTA_MD
JOB_DELTA Execute
RCPTRAN4 report
APO
Current master data in APO
SAP AG 2002
This gives you the chance to periodically schedule the transfer of master data changes as a job. Define a variant (containing the target system and the selection of master data objects) for the RCPTRAN4 report (hidden behind transaction CFP1), and define the job.
(C) SAP AG
SCM612
22
5.23 Integration Model: Other Functions
+
Deactivate integration model Connection between the R/3 and APO Systems for the relevant master and movement data will be cancelled
+
Delete integration model Deactivated models can be deleted
+
Filter object search Check whether the data objects are already contained within an integration model
+
Consistency check You can check the consistency of the selected data in the integration model
SAP AG 2002
Deactivate integration model: For example, relevant sales orders created in the R/3 Systemare no longer transmitted to APO after you deactivate the integration model for movement data (that contains sales and planned orders). Planned orders that are created in APO after deactivation of the integration model are not transmitted to APO either. After you deactivate the integration model for master data, no data changes are transmitted. Delete integration model: Deleting an integration model does not mean that the previously selected data in APO is also deleted. Note: For master data contained within an active integration model for which you have set a deletion flag in the R/3 System, the deletion flag is transmitted to APO using initial data transfer).
(C) SAP AG
SCM612
23
5.24 APO Integration and Master Data : Summary
You are now able to: De scribe the RFC link between the APO and the
R/3 Systems and the R/3 System and the APO System De scribe the APO Core Interface De scribe the R/3 Plug-in technology
Name the APO master data objects De scribe the concept of initial and incremental data transfer of master data from an R/3 System into an APO System Create an integration model for the transfer of master data in a APO TP/VS environment Transfer master data SAP AG 2002
(C) SAP AG
SCM612
24
5.25Exercises Unit: APO Integration and Master Data Topic: APO Integration At the conclusion of these exercises, you will be able to: •
Review the settings of the RFC connection between an R/3 System and an APO System.
Before you familiarize yourself with the functions of the CIF interace, review the RFC connection that connects the R/3 System with the APO System. 1-1
During the exercises, an R/3 System is linked to an APO System. Linking these systems is based on a RFC connection that connects two logical systems. 1-1-1 With which R/3 client are you working? _________________ 1-1-2 View in R/3 Customizing the logical system name assigned to your client. Note the logical name of the R/3 System: ________________ 1-1-3 With which APO client are you working with? ________________ 1-1-4 View in Customizing of the APO System the logical system name assigned to your client. Note the logical names of the APO System: _________________
1-2
In the next step, view the RFC connection between the two systems. 1-2-1 In the R/3 System, display the RFC connection to the APO System. This connection contains the name of the logical APO System that you noted above. Which user name is used for logon to the APO System? ______________________________________ 1-2-2 In the APO System, display the RFC connection to the R/3 System. This connection contains the name of the logical R/3 System that you noted above. Which user name is used for logon to the R/3 System? ______________________________________
(C) SAP AG
SCM612
25
Exercises Unit: APO Integration and Master Data Topic: Master Data At the conclusion of these exercises, you will be able to: • Prepare R/3 material masters for planning in APO • Create a simple integration model for an initial data transfer and execute the transfer. The pump T-F1## should be planned in APO. Therefore, you first prepare the material master in the R/3 for planning in APO, and then create an integration model to transfer into APO. 2-1
The material T-F1## should be planned in APO. A materials planning in the R/3 System is controlled by the MRP type that you enter in the material master. If a material is not to be planned in the R/3 System, it must have the corresponding MRP type. 2-1-1 Display the X0 MRP type in the R/3 Customizing. Which MRP procedure is entered in this MRP type? _________________________________________ 2-1-2 What effect is the effect of this MRP procedure? _________________________________________ 2-1-3 Which planning method is entered in this MRP type (in Additional selection parameters)? _________________________________________
2-2
Change the material master T-F1## in Plant 1000 as follows: 2-2-1 Enter MRP type X0 in the MRP1 view.
(C) SAP AG
SCM612
26
2-3
Create an integration model to transfer the material master to APO: 2-3-1 Generate an integration model with the following settings: Model name: PUMP## Target system: Logical APO system name that you noted above (APOCLNT800) Application:
MAT T-F1##
Select Data Type material masters then scroll down to Relevant Materials area and enter T-F1## and Plant 1000 to be included in the integration model. Do not execute the integration model yet!
2-3-2 Save your settings as variant MAT T-F1##. 2-3-3 Execute the integration model by pressing the execute icon. On the following results screen, make sure that the integration model selected your material T-F1##. 2-3-4 To complete this process Save your integration model. To transfer the master data to the APO System, you must activate the integration model.
2-4
Activate your integration model.
2-5
Check the result of the material master transfers in APO. In the APO System, display the product T-F1## in location 1000. 2-5-1 What is the name of product T-F1##? ______________________________________________ 2-5-2 Look at the Administration tab page. Which user created the product master? ____________________ Where does this user come from? ____________________________________________________ 2-5-3 Go to the Procurement tab page. Which procurement type is set? ____________________________________________________
(C) SAP AG
SCM612
27
5.26Solutions Unit: APO Integration and Master Data Topic: APO Integration 1-1
Document the RFC connection: 1-1-1 R/3 client: Varied, for example, client 800. 1-1-2 Menu path in Customizing of the R/3 System: Basis Components → Application Link Enabling (ALE) → Sending and Receiving Systems → Logical Systems → Assign Client to Logical System Select the table entry corresponding to your client. Select the Details button. Assigned logical name of the R/3 System: Varied, for example, T90CLNT090. Back out to Main Menu 1-1-3 APO client: Varied, for example, client 800. 1-1-4 Menu path in Customizing of the APO System: R/3 Basis Customizing → Application Link Enabling (ALE) → Sending and Receiving Systems → Logical Systems → Assign Client to Logical System Select the table entry corresponding to your client. Select the Details button. Assigned logical name of the APO System: Varied, for example, APOCLNT800. Back out to Main Menu
(C) SAP AG
SCM612
28
1-2
Document the RFC connection to the APO system: 1-2-1 RFC connection to the APO System: Menu path in the R/3 System: Tools → Administration → Administration → Network → RFC Destinations (Select R/3 Connections) – Select APOCLNT800 by doubleclicking. User name:
USERADMIN
Back out to Main Menu 1-2-2 RFC connection to the R/3 System: Menu path in the APO System: Tools → Administration → Administration → Network → RFC Destinations (Select R/3 Connections) – Select T90CLNT090 by doubleclicking. User name:
USERADMIN
Back out to Main Menu
(C) SAP AG
SCM612
29
Solutions Unit: APO Integration and Master Data Topic: APO Master Data 2-1
Menu path in R/3 Customizing: Production → Material Requirements Planning → Master Data → Check MRP Types 2-1-1 MRP procedure in MRP type X0: X, External planning 2-1-2 Effect: This MRP type means that the corresponding materials will not be planned in the R/3. For planned orders that are created manually or transferred from a non-SAP system (APO), a BOM explosion is still performed. 2-1-3 Planning method: 1, Planned with a non-SAP system
2-2
Menu path in the R/3 System: Logistics → Production → Master Data → Material Master → Material → Change → Immediately
2-3 2-3-1 Menu path in the R/3 System: Logistics → Central Functions → Supply Chain Planning Interface → Core Interface Advanced Planner and Optimizer → Integration Model → Generate → Create 2-3-2 Save as a variant: Enter the variant name in the integration model under Goto → Variant → Save as variant and then Save. 2-3-3 Choose Execute. On the resulting screen, double-click on the word Material that appears under the Filter Object heading. Verify that your material has been selected in the model. Choose Save. You should get a message confirming that the Integration Model was generated.
(C) SAP AG
SCM612
30
2-4
Activate your model: Menu path in the R/3 System: Logistics → Central Functions → Supply Chain Planning Interface → Core Interface Advanced Planner and Optimizer → Integration Model → Generate → Activate Verify that your Model, Logical System, and APO Application code is correct on the activation screen. Choose Execute. On the resulting screen, put your cursor on the line containing the date, time and your user-id by clicking on it one time. Choose the Active/Inactive button. A green check mark should appear on the line. Choose the Start button. You should get a message confirming the activation.
2-5
Menu path in the APO System: Master Data → Product, enter product T-F1##, select Location view and enter location 1000, then press the Display button 2-5-1 Name of product: The name is “Pump PRECISION 100” (transferred from the R/3 System). 2-5-2 User who created the product master: The product master was created by user USERADMIN. Origin of this user: The product master was transferred via the CIF interface that is based on a RFC connection between the R/3 and the APO System. The user USERADMIN is defined in this RFC connection – the CIF interface uses this user to logon to the APO System. 2-5-3 Procurement type: Procurement type E (In-house production) is set.
(C) SAP AG
SCM612
31
6 APO TP/VS Master Data
Contents: APO TP/VS-related Master Data Re sult of transfer of R/3 Ma ster Data into APO Supplementing APO Master Data
SAP AG 2002
(C) SAP AG
SCM612
1
6.2 APO TP/VS Master Data: Unit Objectives
At the conclusion of thi s uni t, you will be able to: De scribe the result of the transfer of R/3 TP/VS relevant Master Data into APO Explain the function of the individual Master Data Documents in APO Specify where in the APO System it may be necessary to add to the Master Data transferred from the R/3 System
SAP AG 2002
(C) SAP AG
SCM612
2
6.3 APO TP/VS Master Data: Business Scenario
In preparation for transportation planning using the APO TP/VS component, master data must be transferred to the APO system using the CIF. The PC electronics manufacturer must set up one or more integration models to transfer TP/VS relevant master data to APO.
SAP AG 2002
(C) SAP AG
SCM612
3
6.4 Vehicle Scheduling Process Flow (1) Configuration
Master Data
Modeling
Optimization (Load Consolidation & Vehicle Schedul ing)
Create/Transfer Shipments
Backorder Processing
Create/Transfer Deliveries
Carrier Selection
Carrier Tendering
Release Shipments
SAP AG 2002
(C) SAP AG
SCM612
4
6.5 Master Data: Overview (1)
APO
R/3
APO master data
R/3 master data Plant
Location
Customer Vendor/Carrier Material master
Product
Transportation Zones
Location
SAP AG 2002
The system transfers the R/3 master data objects plant, customer, and vendor into APO as locations with different location types. The system also transfers classes and characteristics from the R/3 into the APO System.
(C) SAP AG
SCM612
5
6.6 Location Types
APO
R/3
Locations with
CIF
location type
Plant
1001 Production plant
Distribution center
1002 Distribution center
MRP area
1007 MRP area
Customer Transportation zone
1010 Customer
Vendor
1011 Supplier
1005 Transportation zone
1020
Carrier
1006 Stock Transfer Point SAP AG 2002
When master data is transferred to APO, the corresponding Location Type is assigned to each master record. The transportation zone in the Customer Master record updates the APO transportation zone table, if an entry does not already exist in the table for the transportation zone. The R/3 Vendor Master does not contain a transportation zone; therefore, the transportation zones used with Suppliers/Carriers must be set up manually in the APO Transportation Zone table.
(C) SAP AG
SCM612
6
6.7 Location Type: Plant
Data transfer from the R/3 plant Customizing: Plant
Master data: Location
Plant
1000
Location
1000
Plant Ham burg
Name
Plant Ham burg
Loc.type
1001
Production plant
Street
Alsterstr. 13
Town
22222 Hamburg
General
APO
Address
Street
Alsterstr. 13
Country DE Germ any
Town
22222 Hamburg
Region 02 Ham burg
Country DE Germ any
Time zone
CET
Region 02
Language
Germ an
Ham burg
Time zone
CET
Language
Germ an
SAP AG 2002
The system transfers a plant into the APO System as a location with location type 1001 (production plant). The system also copies these basic settings for the plant: description, address data, time zone, and regional assignment.
(C) SAP AG
SCM612
7
6.8 Additional Data in APO Location
APO
Master data: Location Location
1000
Loc.type
1001 Production plant
General
Address
TP/VS
...
DE
Plant Ham burg
EN
Plant Ham burg
Short de scription of the location in several languages
Street Alsterstr. 13 Town 22222 Hamburg Country DE Germ any Region
APO-specific planning parameters
02 Ham burg
Time zone
CET
Language
Germ an
SAP AG 2002
For APO locations, you can maintain the short text in several languages (in contrast with the plant in R/3, for example), so that after logon in a certain language, this language appears. As a rule, APO locations contain many additional planning parameters that have no equivalents in the R/3 System. You can then maintain these parameters in APO. The system cannot transfer them from the R/3 System. Enhanced For Transportation Specific Data: • Address/Postal Code Information • Reference Tables for Specifying Compatible/Incompatible Transportation Resources • Lead-Time Buffers (Picking/Packing, Document Creation, and so on) • Loading/Unloading Resources for Inbound/Outbound Shipping • Location Availability/Dock Hours • Transportation Zone Relationship In order to get distance and time proposals, you should maintain the coordinates of a location. The TP/VS tab specifies for each location: If the transportation types must match (‘incompatible/compatible transportation type’) If a load is for one customer only, or if another customer order can be included in the load Time needed for commission Time needed to prepare the transportation First or last point to be delivered For capacity restrictions under Resources tab, define the resources used for loading and unloading a vehicle, or the opening hours of the resource of this location, or whether no resources are needed for loading and unloading.
(C) SAP AG
SCM612
8
6.9 Location Type: Distribution Center
Data transfer from R/3 distribution center (fromRel. 4.0) Customizing: Plant Plant Name
2400 DC Milano
Master data: Location Location 2400
DC Milano
Loc.type 1002
Distribution center
General
Street
Via Castaldi 1
Town
20100 Milano
Country IT Italy
...
APO
Address
Street
Via Castaldi 1
Town
20100 Milano
Country IT Italy
...
Definition as DC Customizing: DRP Plant Node type Name 1000 Ham burg plant 2400 DC DC Milano SAP AG 2002
As of Release 4.0, the R/3 System can define plants as distribution centers, within the frames of the DRP functionality (DRP: Distribution Resource Planning) in the R/3 System. For this, you use the corresponding entry in the Customizing table (Customizing step Assign Node Type - Maintain Plant in the settings of DRP Customizing). When you transfer plants into APO that are defined in the R/3 System as distribution centers, the system transfers them to location type 1002 (distribution center). The transfer of the individual R/3 plant settings (in R/3, a DC is a plant) takes place in exactly the same way as it does for production plants.
(C) SAP AG
SCM612
9
6.10 Location Type: Customer
Data transfer from the R/3 customer
APO
Master data: Customer
Master data: Location
Customer 1000
Location
1000
Becker Berlin
Name
Loc.type
1010
Customer
Becker Berlin
Street
Calvinstr. 36
Town
13467 Berlin
General
Address
Street
Calvinstr. 36
Country DE Germ any
Town
13467 Berlin
Region
Country DE Germ any
11
Berlin
Language
Germ an
Time zone
CET
Control data
Transportation zone D10000
Berlin region
Region
11
Language
Berlin Germ an
Master data: Location Location D10000 Berlin region Loc.type 1005
Transport.zone
SAP AG 2002
The system transfers customers from the R/3 System as locations with type 1010 (customer). The system creates sales orders in the R/3 System and transfers them as transaction data into APO. When the system transfers a customer master from the R/3 into APO, the actual customer location is transferred, as is the transportation zone that is assigned to a customer in the R/3 System, as location type 1005 (transportation zone). You then enter the missing data for use with this transportation zone in the APO planning. You also need a transportation relevant hierarchy. You can maintain the hierarchy in two ways: Implement it manually in APO by attaching the relevant locations in the APO system to the hierarchy Assign the customers in the R/3 System to a transportation zone and transfer the customers to APO. The transportation zones are then created automatically in APO and the corresponding hierarchy entries are created.
(C) SAP AG
SCM612
10
6.11 Location Type: Vendor/Carrier/Service Provider
Data transfer from the R/3 vendor
APO
Master data: Vendor
Master data: Location
Vendor
L1000
Location
L1000 C.E.B. Berlin
Name
C.E.B. Berlin
Loc.type
1011
Street
Kolpingstr. 1
Town
12001 Berlin
General
Vendor
Address
Street
Kolpingstr. 1
Country DE Germ any
Town
12001 Berlin
Region
Country DE Germ any
11
Language
Berlin Germ an
Region
11
Language
Berlin Germ an
SAP AG 2002
The system transfers vendors from the R/3 System as locations with type 1011 (vendor). Note: If the vendor and the customer have the same number in the R/3 System (for example, customer and vendor 1000), then you must rename one of them in the APO inbox, using the customer exit for the vendor master (for example, rename the vendor in S1000). Otherwise, you cannot distinguish between the two locations. The vendor must be known in APO in order for the vendor selection to take place in APO. In the R/3 System, you must specify which account groups from the R/3 vendor master becomes the carrier in the APO System. To do this, choose the CIFVENTYPE table in the data browser (transaction SE16) and confirm with Enter. Branch to the corresponding selection screen. You can use the input help to choose an account group for the R/3 System and a location type for the APO System so that data can be transferred between these two systems. Account group 0005 (carrier) appears as a fixed value, however, you can define other account groups in R/3 Customizing. For the location type on the APO side, the carrier (1020) or supplier (1011) appear.
(C) SAP AG
SCM612
11
6.12 External Procurement Relationship
Data transfer from the R/3 purchasing info record Ext. procurement relationship Purch. info record
APO
General Data Info rec. Vendor known R3CLNT800 Source loc. L1000 in APO? 53004711 Product R-1150
Info rec.
53004711
Vendor
L1000
Material
R-1150
Target loc.
1000
Plant
1000
Valid from
01.01.2000
to
Valid from 01.01.2000 to
Settings Plan.del.time
31.12.9999
Plan.del.time 12 days
31.12.9999
12 days
Transportation lanes Valid 01. 01.2000 to 31.12. 9999
SAP AG 2002
The system can transfer a purchasing info record from the R/3 into APO as an external procurement relationship. You should be aware that the source location (that corresponds with the vendor in the purchasing info record) must be recognized in APO in order for a successful data transfer to take place. If necessary, the system will transfer the vendor beforehand. The system transfers the purchasing price from the purchasing info record into the external procurement relationship (scale prices, too).
(C) SAP AG
SCM612
12
6.13 Master Data: Overview (2)
APO
R/3
APO master data
R/3 master data Plant
Location
Customer Vendor Material master
Product Resource
Transportation Zones
Location
SAP AG 2002
The system will transfer the R/3 material master into the APO System as a product master.
(C) SAP AG
SCM612
13
6.14 Product Master in APO
Views of the APO product master Administration
Demand
Attributes
Lot size
Units of measure
Classification
SNP2
Material
SNP1
PP/DS
Procurement
ATP
GR/GI
SAP AG 2002
The product master in APO is divided into different views according to topic. The header data (tab pages characteristics, units of measure,and classification) is general and valid for more than one location. You can specify the planning of a product in APO according to the location. Locations can come from plant type or MRP area (according to the R/3 storage location MRP areas). Many of the fields for the product are automatically filled when the system transfers a material master from the R/3 System. To guarantee the consistency of the data in the R/3 and APO Systems, only maintain these fields in the R/3 System. The system then only changes the data during a transfer (from the R/3) of the master data changes. You can define the length of the APO product master number in APO Customizing (process step: Determine Output Display Of Product Number). As is standard in R/3, an 18 digit product number is used.
(C) SAP AG
SCM612
14
6.15 Product Master Data
*
Attributes
*
Units of measure
*
Classification Administration
* Global Data
Procurement
Views
Extra
Location Data Views
SNP 2
SNP 1
PP/DS
Demand
GR/GI
Lot Size
ATP
*
Transportation Group =
*
Used to Group Products According to Vehicle Type (For example, Products Requiring Refrigeration)
SAP AG 2002
The Transportation Group is entered in the General Data section under the Attributes tab. The Loading Group is a key that identifies the equipment required to load the goods. For example, a crane or fork lift truck. The Loading Group is entered in the Shipping Section under the GR/GI tab.
(C) SAP AG
SCM612
15
6.16 General Data
R/3
APO
Product A Simple selection in the integration model
Mat A X0
MRP type
X0
MRP procedure
X
Without materials planning,w ith BOM explosion
Attributes Material group
001
Transportation grp
0001
Gross weight
280 KG
Volume
0,75 M3
Units of measure 1 pc
equals
1 pc
1 pal
equals
10 pc
Classification Regarding classes and characteristics that must exist in APO
SAP AG 2002
The system transfers the following general data from the R/3 System material master into the APO product: Material group (Basic data 1), transportation group (Sales and Distribution: gen./Plant), gross weight and volume (Basic data 1), units of measure (Additional data), and classification data (Classification). Note that, for classification data, the system transfers the classes and characteristics into APO beforehand. Materials that the system transfers into APO must be part of the integration model. The selection of APO-relevant materials can usually be easily defined by the use of MRP type X0. In the integration model Create screen this field is labeled MRP characteristic. Materials can also be selected by any combination of the following fields: Material Number, Plant, Material Type, MRP Controller, ABC Indicator, and Plant-specific Material Status.
(C) SAP AG
SCM612
16
6.17 Maintaining Additional Product Master Fields in APO
Mass maintenance for product master fields in APO (for those that cannot be transferred from the R/3 System) Alternative solution using modification: Enhancement of the R/3 material master record with customer-specific fields (Append structures) and transfer of these fields in the integration model (using a customer exit)
SAP AG 2002
Use mass maintenance to subsequently maintain product master records that you have copied from R/3 (call from the initial screen in product master maintenance). In mass maintenance, for example, you can maintain fields that are not transferred from R/3, because these fields do not exist. Alternative solution using modification: You can extend the R/3 material master using customerspecific fields (Append structures, see SAP note 44410). You can also enhance the R/3 material master, to maintain the settings for functions that do not exist in R/3 in the R/3 material master. For the CIF transfer for these fields, you need to note that you need to enhance CIF in the R/3 outbox and the APO inbox to define that these fields are transferred (customer exits for material masters).
(C) SAP AG
SCM612
17
6.18 Resources
Transport (T)
Vehicle Resource (T)
Calendar
Handling Unit (H)
SAP AG 2002
Transportation planning relevant resources are Transport (T), Vehicle Resource (T), Calendar, and Handling Resource (H). Transport resources are only used by SNP. The resource category (T, H) determines the usage of a resource. They are for descriptive purposes only and do not play a role in planning. TP/VS resources are created manually.
(C) SAP AG
SCM612
18
6.19 Transportation Planning Resources
Single or multi-resource s
Capacity for loading/unloading
Vehicle resource s
Capacity of a specific transportation type
Calendar
Specification of working da ys
SAP AG 2002
(C) SAP AG
SCM612
19
6.20 Single Resource Example Single or multi-resource s
Capacity for loading/unloading
SAP AG 2002
A single resource upon which only one activity can be executed at a time has a dimension-free capacity of one. For single resources the capacity value is fixed in the system. A single resource can have only two different situations; either it is loaded with an activity or it is not loaded at all. Multi resources are used to map resources on which several activities can be carried out at a time. The maximum number of activities that can be scheduled at the same time depends on the organizational or technical conditions for the resource. Path: SAP menu→Master Data→Resource A Handling Resource (Resource Type H) is an example of a single or multi-resource that is used in TP/VS. Loading and unloading equipment such as fork-lifts are examples of this type of resource. Capacities in the form of available working hours including downtimes are specified for the handling resource.
(C) SAP AG
SCM612
20
6.21 Vehicle Resource Example) Vehicle resource s
Capacity of a specific transportation method
SAP AG 2002
Vehicle Resource (TP/VS) Individual or Single Capacity (by weight/volume) A full load equals the maximum capacity of the resource The vehicle resource is a multidimensional resource. It can have six dimensions in maximum. The available capacity of this resource type cannot be maintained on a time-dependent basis. If
you do need to maintain limited availability, you can do so by means of shift sequences. Key Consideration: During Optimization, resources are considered according to Type/Method and Independent of a Carrier Solution for Aligning with Carrier Capabilities and Geographical Coverage For Identical Resources, Create Multiple Vehicle Types/Methods in accordance with Carriers
(C) SAP AG
SCM612
21
6.22 Transport Method Transport Method
Basis for a Group of Resources
Created in IMG
SAP AG 2002
Path: IMG → Advanced Planner and Optimizer (APO) → Supply Chain Engineer (SCE) → Maintain Transport Method The first column (labeled Vehicle), is also called the Transportation Method. The transportation method describes the vehicle used for shipments between locations. If you set the flag Own means of transport the following applies to vehicles of the means of transport in the optimization : You start at the beginning of the optimization run with the last location On completion of the route planned by the optimizer, you must return to the depot location provided that a depot location is maintained (resource master data). In particular there must be a transport link from the last unloading location back to the depot. Otherwise, the optimizer cannot carry out these return journeys, and no transport is generated. The entire vehicle route generated by the optimizer generates a single transport. Example: you want to transport two orders from A to B using one vehicle; every order fills the vehicle. The vehicle is assigned to the depot location A. → The optimizer plans a route A-B → AB → A. The transport includes the sections A-B → A-B. With a third-party means of transport you would get two transports, A-B in each case.
(C) SAP AG
SCM612
22
6.23 Transportation Lane
Distr.Center
Transportation Lanes Customer
Plant
Customer
SAP AG 2002
A transportation lane represents a direct route between two locations that can be used to source and transport products. Each lane is defined by its source and target locations, depending on the direction and its assigned products to be transported along the lane. Each lane is also assigned available transportation methods. Transportation lanes can be maintained individually or in groups. Mass maintenance of transportation lanes facilitate the generation and maintenance of large quantities of transportation supply chain data. The supply chain network is represented by the locations and their connected transportation lanes. Considered part of APO master data, transportation lanes usually remain unchanged over an extended period of time. The following APO components make use of transportation lanes: Supply Network Planning Network Design Production Planning TP/VS
(C) SAP AG
SCM612
23
6.24 Transportation Lanes Information A ssigned to a Lane: Source and target location Product procurement
Choice of products assigned to lane
Validity
Date from Date to Carriers
Location
Transportation costs
Share of business
Priority
SAP AG 2002
The information in the tab Product Procurement is not used in VS. There is a mass create function for creating transportation lanes. A carrier will be assigned in a lane under the transport type Allocate carrier. The carrier has to be defined as a location (location type 1020). To do this, an additional tab Carrier is available.
(C) SAP AG
SCM612
24
6.25 Transportation Lanes Transportation Method
Choice of transportation method
Validity
Date from Date to
Parameters used in VS
Transport time (in hours, m inutes) Transport distance Transportation costs for a unit of product
Cost for transportation method (per km)
SAP AG 2002
Controls: Check the box for Det. Planning is ON If you want to use SNP, check Aggr. Planning Discrete transportation method is used in SNP The system proposes time and distance of transportation based on the coordinates of the locations. You can maintain real data and set the flag for Fixed Transport Duration and Fixed Transport Distance.
(C) SAP AG
SCM612
25
6.26 TP/VS Supply Chain Modeling - Hierarchies
Outbound
Transportation Zone Hierarchies
Replenishment
Inbound
Master Transportation Lanes Runtime Lane
SAP AG 2002
There are two types of hierarchies used in VS: Transportation zone hierarchies to allocate a location to customers/plants/DCs so that they are served via one transportation lane Carrier Hierarchy structures used to create multiple modal shipments Transportation zone hierarchies are used to group shipping origins or destinations to reduce the number of transportation lanes that have to be maintained. A transportation lane can be maintained between: A location and a transportation zone Two transportation zones A transportation zone
You can maintain the hierarchy in two ways: Implement it manually in APO by attaching the relevant locations in the APO system to the hierarchy (transportation zones as level 1 node, customers as subordinated level 2 node) Assign the customers in R/3 to a transportation zone and transfer the customers to APO: the transportation zones are then created automatically in APO and the corresponding hierarchy entries are created.
(C) SAP AG
SCM612
26
6.27 Distance/Duration Calculation Runtime Lane Distance 104 Runtime Lane Geo Distance 80
Maintained Master Lane Distance 130 Master Lane Geo Distance 100
Distance Calculation Runtime Geo Distance 80 X
Maint. Master Lane 130 Master Geo Distance 100
= Actual Runtime Distance 104
Duration Calculation Distance / Average Speed Per Unit SAP AG 2002
TP/VS will compute the runtime lanes during optimization. Corresponding transportation lanes are generated between all locations assigned to the transportation zones. In the process, the cost information is taken from the transportation lanes maintained. The distance/duration is calculated according to the settings or taken from the transportation lane maintained. The maintained distance in the Master Lane includes a factor for road/street map variability. The Factor is obtained from the Maintain Transport Method table in Customizing. This factor establishes the proportion between the linear distance between two locations and the actual distance covered by the vehicle transporting goods between them. Included in the Maintain Transport Method table is the Average Speed of the transport method. The Runtime distance is divided by the average speed to calculate the estimated Duration.
(C) SAP AG
SCM612
27
6.28 Transportation Zone (Location) Hierarchy
Transportation Zone Hierarchi es are assigned to the SC Model and di splayed in the Work Area SAP AG 2002
To set up a hierarchy: Create a hierarchy in Customizing Specify these hierarchies in the TP/VS→Basic Settings→ Maintain Transportation-Relevant Hierarchy table in Customizing of APO. Define the hierarchy application-wise in master data (get the transportation zone via CIF from R/3) Assign the hierarchy to the active model in SCE if not from CIF. To see it in SCE, set the Display hierarchies option in the SCE User-specific settings at menu path: SAP Menu→Master Data→Supply Chain Engineer→Make Settings. Note: A Circular relationship must be set up for creating intra-zone connections. To do this, create a transportation lane with the source and target locations as the same transportation zone (= Intra-zone Lane).
(C) SAP AG
SCM612
28
6.29 Carrier Structure Hierarchy
SAP AG 2002
TP/VS offers a trans-shipment function in conjunction with shipping using multiple modes of transportation or the transfer of orders between vehicles. Trans-shipments are shipments for which one or several orders must be transferred from one vehicle to another at some stage between the start and destination locations of the order(s). This may involve vehicles of different types with different modes. Shipments of this kind can only be generated using the Optimizer. It is not possible to create them manually using interactive planning. The following data must be maintained so that the Optimizer can generate the shipments required: Create a two-level location hierarchy structure in Customizing In Customizing, enter this structure as the hierarchy structure for the transportation service provider (transshipment structure). For this, choose TP/VS → Basic Settings → Maintain Transportation-Relevant Hierarchy Create a hierarchy for this structure Assign the hierarchy to model 000 Maintain the hierarchy
(C) SAP AG
SCM612
29
6.30 Hierarchy: Example 1
Plant
DC Customers
Structure of a hierarchy w ith one stock transfer point
SAP AG 2002
Hierarchies can be maintained and displayed at: SAP Menu: Master Data → Hierarchy In this scenario, the DC represents a load transfer/consolidation point or cross-docking location. For example, several orders are transported from a plant by truck to a DC and then they are distributed to several customers using smaller trucks.
(C) SAP AG
SCM612
30
6.31 Hierarchy: Example 2
Rail Truck
DC1
DC2
Plant
Truck
Customer
Structure of a hierarchy w ith two stock transfer points, multiple modes of transportation
SAP AG 2002
In this example, a customer shipment is made using multiple modes of transportation, Truck and Rail. The DCs represent load transfer points, such as rail yards and ports. Between a plant/DC and a customer (Outbound shipments) or Vendor and Plant/DC (Inbound shipments) there cannot be more than two stock transfer points. If stock transfer points are used, there can be one alternative direct lane between a plant/DC and customer for outbound shipments or vendor and plant/DC for inbound shipments. Which lane is chosen depends on the maintained costs per lane. A transfer transport generated by the optimizer can be edited manually. The times can be changed and orders can be taken from the transport. It is not possible to add orders to the transport manually.
(C) SAP AG
SCM612
31
6.32 Example: Roundtrip outbound from one location
vehicles trip source-destination Depot (as a warehouse) Deliver
One source, multiple destinations
Pickup
SAP AG 2002
(C) SAP AG
SCM612
32
6.33 Example: Round trip inbound into one location
vehicles trip source-destination Depot (as a warehouse) Deliver Pickup
One destination, multiple sources
SAP AG 2002
(C) SAP AG
SCM612
33
6.34 Example: Mixed round trip to and from one location Note: You can create mixed inbound and outbound in APO, but R/3 can not process these shipments
vehicles trip source-destination -
One location as source or destinations for all other locations
Depot (as a warehouse) Deliver Pickup
SAP AG 2002
(C) SAP AG
SCM612
34
6.35 Example: Multi stop - no return
vehicles trip source-destination Depot (as a warehouse) Deliver Pickup
Orders with different sources and destinations
SAP AG 2002
(C) SAP AG
SCM612
35
6.36 Example: Scheduled vehicles Note:
For example, trains, ships
arrival time = departure time
2:00 pm 07:00 pm 1:00 pm 06:00 pm
3:00 am 08:00 pm
5:00 am 10:00 pm
station
Opening hours of locations are not considered when using scheduled resources
vehicles trip
10:00 am 03:00 pm
source-destination -destination Depot (as a warehouse)
8:00 am 01:00 pm
Deliver Pickup
SAP AG 2002
(C) SAP AG
SCM612
36
6.37 Note: More complex problems ...can be solved by decomposing the transport network ... can be solved by decomposing the transport network
Assignments: S1 - IDC
Assignment: IDC - ODC
S2 - IDC
C1
S2
C2 IDC
ODC
C3
S4 Supplier
1) Opti mize pick up as a t otall y separate problem.
ODC - C2
S1
S3
Decompose:
Assignments: ODC - C1
C4 Inbound DC
Outbound DC
Customer
2) Source is now no longer S1 but IDC. 3) Establish lane bet ween IDC and C1. 4) Have t he optimizer s hip either: IDC - ODC - C1, or: IDC - C1
Note: This onl y wor ks if the ship from and ship to addresses are changed appropriatel y
SAP AG 2002
(C) SAP AG
SCM612
37
6.38 APO TP/VS Master Data: Unit Summary
You are now able to: De scribe the result of the transfer of R/3 TP/VS relevant Master Data into APO Explain the function of the individual Master Data Documents in APO Specify where in the APO System it may be necessary to add to the Master Data transferred from the R/3 System
SAP AG 2002
(C) SAP AG
SCM612
38
6.39Exercises Unit: APO TP/VS master Data Topic: Master Data Integration Model At the conclusion of this exercise, you will be able to: •
Create, generate and activate an R/3 Integration Model to transfer, via the CIF, the master data needed in the TP/VS component of the APO system.
•
Check the master data transfer settings in the R/3 System
•
Create transportation lanes in APO Master data.
•
Display APO master data
Before setting up the optimization and planning environment in TP/VS, the pertinent master ond organizational data must exist in APO. Most of this master data will come from the R/3 (OLTP) System. Relevant Customer, Vendor/Carrier, and Material master data must be transferred and maintained via the CIF. In addition, organizational data such as Plants and Transportation Planning Points must be transferred also. As a member of the TP/VS implementation team, it is your job to set up the integration model to perform this initial transfer and any subsequent transfer that will be required. 1-1
Create, generate, and activate an integration model, GR##, in R/3 to transfer the following master and organizational data to the target APO system: Material masters Plants Customers Vendors Transportation Planning Point
(C) SAP AG
SCM612
39
1-1-1 Create the integration model: GR##. Use MD as your Application code. Restrict your master data selection to that data that belongs to your group number. Use the following table as a basis for creating your model: Master Data Object
Data to Select
Material master records
T-ATC1-## T-ATD2-## T-ATD3-##
Customer master records
T-S11A## T-S22A## T-S33A## T-S11B## T-S11C## T-S090## T-S200##
Vendor Master records
T-S100## T-S11F## T-S11H##
Shipments*
TPPt: AP##
*Note: You must select Shipments to get your Transportation Planning Points transferred to APO. Restrict Selection of Material Master records to the following plants: 10##, 12##, 22##, 25## Save the settings as a variant: GR##-MD 1-1-2 Generate the model. 1-1-3 Activate the model.
(C) SAP AG
SCM612
40
1-2
In the APO system, using the master data displays, verify that the following master data was transferred: Location Master Data: T-S11A##: What is the Transportation Zone: _______________________________ T-S11C##: What is the Transportation Zone: _______________________________ T-S11F##:
What is the Transportation Zone:
_______________________________ Product Master Data: T-ATC1-##: What is the Transportation Group? _________ What is the Gross Wgt?: _________________ What is the Volume?: ___________________ T-ATD2-##: What is the Transportation Group? _________ What is the Gross Wgt?: _________________ What is the Volume?: ___________________ 1-3
Now that you have locations in APO master data, you will establish some transportation lanes between your plant 10## and your Customers. The remaining lanes will be created in a later unit. Create the lanes within Model 000. Set the Product Procurement area to All Products. Put Group ## in the Header Description. 1-3-1 Create transportation lanes between Plant 10## and customers T-S11A##, T-S22A##, T-S33A##, T-S11B## and T-S11C##. Remember, you should also create a transportation lane going from the customer to the plant/DC.
(C) SAP AG
SCM612
41
1-4
Check the settings for the transfer of master data from the R/3 System to APO using transaction CFC5. Just document them. DO NOT CHANGE THEM. 1-4-1 Material Master: ___ Bus.Transaction Event, Immed. ___ ALE change pointer, periodic ___ No change transfer 1-4-2 Customers: ___ Bus.Transaction Event, Immed. ___ ALE change pointer, periodic ___ No change transfer 1-4-3 Vendors: ___ Bus.Transaction Event, Immed. ___ ALE change pointer, periodic ___ No change transfer.
(C) SAP AG
SCM612
42
6.40Solutions Unit: APO TP/VS master Data Topic: Master Data Integration Model 1-1
Create, Generate, and Activate your Master Data Integration Model: 1-1-1 Create the integration model: R/3 SAP Standard Menu: Logistics → Central Functions → Supply Chain Planning Interface → Core Interface Advanced Planner and Optimizer → Integration Model → Generate → Create Enter Model Name:
GR##
Enter Target System: your APO logical system Enter Application:
MD
In the Add to integration model check boxes, set the following: Material masters Plants Customers Vendors Shipments In the Relevant Materials selection box, enter your material numbers by first selecting Multple selection on the Material line. In the Single vals tab enter your material numbers. Choose Copy. In the Plants line, choose Multiple selection and enter the plants for which to copy the material masters in the Single vals tab. Choose Copy. In the Customers selection box, enter your Customer numbers using the same method as that used in Material Master selection. In the Vendors selection box, enter your Vendor numbers using the same method as that used for the Material and Customer selection. In the Shipments selection box, enter your Transportation Planning Point in the first field. Before the model is generated, create a Variant of the model. This variant is necessary if you want to run the model in a background process later. Choose Save. In the ABAP Variant screen, enter your variant name: GR##-MD and a description of your own choosing. Choose Save. 1-1-2 Generate the model. (C) SAP AG
SCM612
43
Choose the Execute icon. Upon completion of the model generation you will get a message indicating the model was generated. 1-1-3 Activate the Model. R/3 SAP Standard Menu: Logistics → Central Functions → Supply Chain Planning Interface → Core Interface Advanced Planner and Optimizer → Integration Model → Generate → Activate Enter your Model, Logical System and APO Application code if not present in the fields. Choose Execute. Place your cursor on the line with the Date, Time and User-ID. Select the Active/Inactive button. A green check mark should appear next to the line indicating that the model has been made active. Select Start to actually transfer data to the APO system. After the transfer has been activated, you will get a confirmation message. 1-2
Verify the Location data: APO: SAP Menu: Master → Location → Location Enter the Location Number in the Location field and select Display. For the Transportation Zone code, Select the TP/VS tab. Verify the Product Master data: APO: SAP Menu: Master → Product Enter the Material Number in the Product field . Set the View to Global Data. Select Display.
1-3
Create the Transportation Lanes. APO: SAP Menu: Master → Transportation Lanes 1-3-1 Create Plant/DC to Customer Lanes. Model Name: 000 Source loc.: 10## Target loc.: Customer location number Choose Create. Choose Header data. Enter Group ## in the Description field. Choose Copy and Close (green check mark). In the Product Procurement section, select Creation of a new entry. In the Product Procurement box that is displayed on the right side of the screen, select the All Products.
(C) SAP AG
SCM612
44
Enter today's date in the Start date field in the Validity box. Enter '12/31/9999' in the End date field in the Validity box. Choose Copy and Close. Choose Save. Perform these steps for all remaining combinations of the plant and Customer locations in the list. 1-4
Document the setting for the transfer of master data from R/3 to APO: R/3 SAP Standard Menu: Logistics → Central Functions → Supply Chain Planning Interface → Core Interface Advanced Planner and Optimizer → Settings → CFC5 - Change transfer 1-4-1 ,2, and 3 Document the setting from the screen.
(C) SAP AG
SCM612
45
7 Models and Planning Versions
Contents: Models and Planning Versions for Master Data and Transaction Data Maintaining Models via the Supply Chain Engineer
SAP AG 2002
(C) SAP AG
SCM612
1
7.2 Models and Planning Versions: Unit Objectives
At the conclusion of thi s uni t, you will be able to: Create Models and Planning Versions for Master Data and Transaction Data Maintain Models via the Supply Chain Engineer
SAP AG 2002
(C) SAP AG
SCM612
2
7.3 Models and Planning Versions: Business Scenario
The PC electronics manufacturer creates multiple models for transportation planning and each one can have multiple versions.
SAP AG 2002
(C) SAP AG
SCM612
3
7.4 Models and Planning Versions
Master data
Non Non-R/3 R/3 System System
R/3
Master data in APO
Simulation model n
Simulation model Z01 Active model 000 Locations
Resources Resources
Resources
Products
PPM
PPM Planning Planning vv ersion ersion n+1 n+1 Version-depende Version-dependent nt master master data data and and transaction transaction data data
Transportation lane
Activ Activ ee planning planning vv ersion ersion 000 000 Version-depende Version-dependent nt master master data data and and transaction transaction data data
PPM
Planning Planning vv ersion ersion 11 Version-depende Version-dependent nt master master data data and and transaction transaction data data
Planning Planning vv ersion ersion nn Version-depende Version-dependent nt master master data data and and transaction transaction data data
SAP AG 2002
The Supply Chain Model (abbreviated as model) represents the entire supply chain network, ranging from suppliers over production and distribution sites up to the customer. It includes locations, transportation lanes, products, resources, and Production Process Models (PPM). Thus, the model is the basis for all planning functions in APO. It contains only master data and it is modeled in the Supply Chain Engineer. Master data from the R/3 System (or a non-R/3 System) is automatically assigned to the active APO model (model 000) during the master data transfer to the APO System. The active model represents the supply chain actually used in the enterprise. In this way, all master data transferred is automatically available for operational planning in the APO model 000. Master data that you create manually in APO must be explicitly assigned to one model. If you want to plan another supply chain (for example, a different distribution center) in the simulation, you can create an inactive model in APO. If you want to use certain master data in both the active and inactive model, or in the inactive model alone, you must assign this master data to the inactive model. You can either use the Supply Chain Engineer (SCE) as the modeling tool in APO or a manual assignment from within master data maintenance (from the R/3-APO interface, master data is automatically assigned to the active model only). For simulation purposes, you can create several planning versions for a given supply chain model. Note that only model 000 and planning version 000 are active. The planning version comprises master data and transaction data. In an inactive planning version, you can, for example, simulate increased planned independent requirements and plan production based on an increased demand. You cannot transfer the planning results from the inactive planning version to the active version. You must repeat the planning in the active planning version. You can use version management to copy models and planning versions or create them manually. Their names must be unique, which means that there cannot be two planning versions of the same name in different models. The active planning version 000 only exists in model 000.
(C) SAP AG
SCM612
4
7.5 Models and Planning Versions for Locations and Products
R/3
APO
R/3 Master Data
APO Ma ster Data
Simulation model Z01
Active model 000 Plant, customer, vendor Material m aster
Assignment
Activ Activ ee planning planning vv ersion ersion 000 000
Create master data
Locations Products
Reference Reference
Planning Planning vv ersion ersion 001 001
Locations Products
SAP AG 2002
Maintained during master data transfer
Planning version-specific fields may be added (only valid in version 001) Master data added
If locations and products are created in APO via the R/3-APO interface, they are automatically created in the active planning version 000 and assigned to the active model 000. If planning is simulated in an inactive planning version (for example, planning version 001), the master data fields of the location and the product master of the active planning version 000 are read (location and product in an inactive planning version thus refer to the active planning version 000). If you want to use modified master data in simulated planning (for example, different MRP attributes of a product), you can maintain certain fields specifically for the planning version in the location or the product master in APO (manually or mass maintenance). During planning in planning version 001, these version-specific fields from planning version 001 are then read. For fields that are specific to a planning version, and can be maintained as such, the system reads the fields from active planning version 000 (reference) if no alternative settings have been made. If you want to use certain locations and products in inactive models, you must manually assign these locations and products to the inactive model required. You can do so from within master data maintenance or via the Supply Chain Engineer. Within the inactive model, planning can be carried out in one or several inactive planning versions.
(C) SAP AG
SCM612
5
7.6 Models and Planning Versions for Resources
R/3
APO
R/3 Master Data
APO Ma ster Data
Simulation model Z01
Active model 000
Capacity
Create master data
Resource
Copy
Activ Activ ee planning planning vv ersion ersion 000 000
Copy
Resource Planning Planning vv ersion ersion 001 001
Resource
SAP AG 2002
Assignment
Independent Independent of planning vv ersion ersion
Maintained during master data transfer
Planning version-specific fields may be added (only valid in version 001)
Master data added
If resources are created in APO via the R/3-APO interface, they are automatically created in a planning version-independent version 000 (planning version blank) and assigned to the active model 000. In addition, these planning version-independent resources are automatically copied into all planning versions (active planning version 000 as well as all inactive planning versions) that exist in this model during master data transfer. You are left with a planning version independent resource, an active planning version resource, and inactive planning version resources. When version management is used to create a new planning version at a later stage, all resources are automatically copied to the new planning version (as a copy of the planning version-independent resource) when the new version is created. If planning is simulated in a certain planning version (for example, in the active planning version 000 or the inactive planning version 001), the resource master data fields in the relevant planning version are read. If you want to use modified master data in the simulated planning (for example, different operating times of resources in simulation), you can change the resources specifically for a planning version in APO. If you also want to use certain resources in inactive models, you must manually assign these resources to the required inactive model. You can do so from within master data maintenance or via the Supply Chain Engineer. When you assign the resource to the inactive model, the resource is automatically created in all planning versions of the inactive model (copy of the planning versionindependent resources to the planning version-specific resources of the active model). If you do not work in the active model and version (000) and you use TP/VS, only consolidation is possible. Carrier Selection and Publication of Orders and Deliveries are not possible.
(C) SAP AG
SCM612
6
7.7 Supply Chain Engineer (SCE) as the Modeling Tool for Models
Network structure
Work area folder Planning objects
Network map
SAP AG 2002
Maintain the supply chain network in the Supply Chain Engineer (SCE), by placing locations on the map and create a network by adding transportation lanes. The lane direction shows the direction of the product transportation flow. The SCE enables you to look at the data that belongs to particular elements in your supply chain. In addition, it allows you to maintain the model objects simultaneously. You can make queries about information via individual or combined elements in your supply chain. For example, you can query a list of all the products belonging to a specific location in your model. At the same time, you can add products to this location or make changes in the location master.
(C) SAP AG
SCM612
7
7.8 Objects in the Supply Chain Engineer
● Locations Vendor
Plant
DC
● Transportation
Customer Transport- MRP area ation zone lanes
Stock transfer Carrier point
SAP AG 2002
The supply chain model also allows you to keep track of other supply chain elements, as well as locations and transportation lanes. These include products, PPMs (production process models), and resources. You may have to assign or delete large numbers of objects in your model during supply chain modeling. Many of these objects have dependent objects assigned to them. To guarantee consistency within the model, you can automatically assign or delete the dependent objects, together with the primary object. Automatic assignment guarantees not only consistency but also enables easier model maintenance.
(C) SAP AG
SCM612
8
7.9 Work Areas in the Supply Chain Engineer
Access to frequently used objects Used for queries Serve as filters Configured for users
SAP AG 2002
If you have a lot of master data, viewing it in the network map in the Supply Chain Engineer can become very confusing. To limit your view to only the master data you want to concentrate on, define work areas. The work area is used exclusively as a filter for displaying objects in the Engineer. You can maintain different work areas. This enables you to obtain manageable amounts of data. In the work area of the Supply Chain Engineer, you can select: Locations (plant, distribution center, vendor, and customer) Products Resources Production Transportation Lanes
(C) SAP AG
SCM612
9
7.10 Models and Planning Versions: Unit Summary
You are now able to: Create Models and Planning Versions for Master Data and Transaction Data Maintain Models via the Supply Chain Engineer
SAP AG 2002
(C) SAP AG
SCM612
10
7.11Exercises Unit: Models and Planning Versions Topic: Supply Chain Engineer At the conclusion of this exercise, you will be able to: • •
Create a model of a supply chain network. Use the Supply Chain Engineer to view and maintain a network.
After creating the APO Master data consisting of Locations (plants/DC's, vendors and customers), Products, Resources and Transportation Lanes a network can be created using the Supply Chain Engineer. This network can be used to limit the amount of data that is viewed for a given supply chain scenario. A Work Area can be created for each network scenario. You will create a work area representing your supply chain network. 1-1
Create a new Work Area, GR##, for Model 000 for your supply chain network. 1-1-1 Add the following Plants to your work area: 10## 12## 22##
Hamburg Plant Dresden Plant Paris Plant
1-1-2 Add the following Distribution Center to your work area: 25##
Rotterdam Distribution Center
1-1-3 Using the Connect icon on the network map, create a transportation lane between plant 12## and plant 22##. 1-1-4 Add your customers locations to the work area: T-S11A## T-S22A## T-S33A## T-S11B## T-S11C##
(C) SAP AG
CompuMax GmbH PILAR am Neckar DELA Handelsgesellschaft mbH PC-World Stuttgart KG Riedel Computer OHG
SCM612
11
1-1-5 Add your vendors to the work area: T-S11F## T-S11H## T-S100##
Sunny Electronics GmbH PAQ Deutschland GmbH Intercompany Vendor for Plant 22##
1-1-6 Add your products to the work area: T-ATC1-## T-ATD2-## T-ATD3-##
Sunny Sunny 01 Maxitec R 3200 Personal computer Diskette Drive, 3.5", HD
1-1-7 Display the list of transportation lanes for the model. 1-1-8 Save the work area.
(C) SAP AG
SCM612
12
7.12Solutions Unit: Models and Planning Versions Topic: Supply Chain Engineer 1-1
Create a new Work Area for Model 000 for your supply chain network: APO SAP Menu → Master Data → Supply Chain Engineer → /SAPAPO/SCE01 Maintain Model 1-1-1 Enter Model 000 Enter Work Area: GR## Choose Change. In the Location tab, right-click on the word Plant next to the plant icon. Select Add objects to work area. The Select work area dialog box will appear. Enter the plants in the Internal char. value fields. Choose Copy. The plant icons representing your plants will appear on the map and will be listed. 1-1-2 Right-click on the words Distribution Center next to the DC icon. Select Add objects to work area. Select work area will appear. Enter the distribution center, 25##,in the Internal char. value fields. Choose Copy. The plant icons representing your plants will appear on the map and will be listed. 1-1-3 Create a transportation lane from plant 12## to plant 22## using the Connect icon. Select the Connect icon located in the toolbar above the map. Put your cursor on the plant 12## icon and Drag&Drop a transportation lane to plant 22##. When the left mouse button is released, the system will display the transportation lane create screen. Select the Header data button. When the header data General data box appears, enter Group ## in the description field. Choose Copy and close. Select Create in the Product Procurement area. When the Product Procurement box is displayed, select All Products and enter today's date in the Start date field and 12/31/9999 (if your date format is different, then use it) in the End date field. Choose Copy and close.
(C) SAP AG
SCM612
13
Choose Back. The system will return you to the SCE. 1-1-4 Right-click on the words Customers/Ship-to party next to the Customer icon. Select Add objects to work area. Select work area will appear. Enter the customer location numbers in the Internal char. value fields. Choose Copy. The customer location icons representing your customers will appear on the map and will be listed. In addition, lines with directional arrows will appear representing the transportation lanes between the plants and the customers. 1-1-5 Right-click on the word Suppliers next to the Supplier location icon. Select Add objects to work area. Select work area will appear. Enter the supplier location numbers in the Internal char. value fields. Choose Copy. The supplier location icons representing your customers will appear on the map and will be listed. In addition, lines with directional arrows will appear representing the transportation lanes between the plants and the suppliers. 1-1-6 To assign your products to the work area, select the Products tab first. Then right-click on the word Products to the right of the Products icon. Select Add objects to work area. Select work area will appear. Enter the product numbers in the Internal char. value fields. Choose Copy. Your products will appear in a list under the Products icon.
(C) SAP AG
SCM612
14
1-1-7 Display the list of transportation lanes that exists in Model 000 by first selecting the right arrowhead the the right of the tabs until the Transportation lane tab comes into view. Select the Transportation lane tab. The list of transportation lanes will appear. Find one of the transportation lanes in your network and double-click on it. The system will take to the transportation lane change transaction. Choose Back to return to the SCE. 1-1-8 Choose Save to save your work area.
(C) SAP AG
SCM612
15
8 Transfer of Transaction Data
Contents: Transfer of Transaction Data between the R/3 and APO Systems Initial and Incremental Transaction Data Transfer Integration Model for the Transfer of Transaction Data Publication of Delivery and Shipment data from the APO to the R/3 System s
SAP AG 2002
(C) SAP AG
SCM612
1
8.2 Transfer of Transaction Data: Unit Objectives
At the conclusion of thi s uni t, you will be able to: De scribe the process of Transaction Data transfer between R/3 and APO System s Define an Integration Model for the transfer of Transaction data Make the required customizing settings in APO to facilitate the publication of delivery and shipment data from APO to the R/3 System Transfer Transaction Data from the R/3 System to the APO System
SAP AG 2002
(C) SAP AG
SCM612
2
8.3 Transfer of Transaction Data: Business Scenario
Sales orders, purcha se orders and stock transport orders must be transferred to APO using the CIF for transportation planning. An integration model will be created to transfer the transaction data to APO. Upon completion of the transportation planning for a group of sales orders, the resulting delivery and shipment documents must be transferred to the R/3 System using the publication proce ss. Before thi s proce ss can be performed, customizing settings in APO must be completed.
SAP AG 2002
(C) SAP AG
SCM612
3
8.4 Transaction Data Interface: Core Interface (CIF)
APO
R/3 R/3 tran saction data Purchase orders Purchase requisitions Sales orders Planned orders Planned ind.reqmts Reservations Stocks and so on
APO transaction data Core Interface
CIF Integration model
Orders - Replenishment order - Manufacturing order - Procurement order and so on (distinction by ATP category)
SAP AG 2002
The transaction data that is to be transferred into APO is specified in an integration model you define in the R/3 System. The transaction data is mapped to orders in APO that differ by ATP category.
(C) SAP AG
SCM612
4
8.5 Transaction Data Objects of the CIF
APO
R/3 R/3 transaction data Purchase orders
Initial data transfer
Purchase requisitions Sales orders Planned orders Planned ind.reqmts Reservations Stocks ...
Incremental data transfer
APO transaction data Order with category BF (PchOrd) AG (PurRqs) BM (SalesOrder) AI (PlOrd.) FA (FC req.) AM (PrdRes) CC (Stock) ...
Realtime SAP AG 2002
The initial data transfer of transaction data is performed via the APO Core Interface (CIF). This is usually automatically followed by the incremental data transfer between the R/3 and APO Systems for transaction data objects that are members of an active integration model. New transaction data or changes to existing transaction data are transferred automatically.
The APO transaction data objects are generally not identical to those of the R/3 System. The system transfers various R/3 transaction data into APO as orders that differ by ATP category.
(C) SAP AG
SCM612
5
8.6 Initial Data Transfer of Transaction Data: Overview
1. Generate integration model
Name Target sys.
Determine name and APO target system
Sales orders Production/process ord ers Storage lo cation stock
Select transaction data
...
2. Activate integration model Integration model is active Start
Initial transfer of transaction data is performed, followed by a continuous real-time incremental data transfer
SAP AG 2002
Define the integration model that controls the transfer of transaction data in the R/3 System. You can find the menu option Core Interface Advanced Planner and Optimizer (the CIF menu) under Logistics → Central Functions → Supply Chain Planning Interface.
The integration model distinguishes between master data and transaction data. Select the two types of data in separate integration models and then transfer them separately.
Select the transaction data you want to transfer in the integration model. Specify the following in the integration model:
The APO target system for the data transfer
The data objects you want to transfer
You can delete integration models that you no longer need, but you must first deactivate them.
The system usually performs a continuous real-time incremental data transfer between the R/3 System and APO for any transaction data from the production planning that is contained in an active integration model.
(C) SAP AG
SCM612
6
8.7 Integration Model for Transaction Data Name + application = unique definition of integration model Name
PC
Target sys.
APOCLNT800
Application
TD
APO System
Sales orders Production/process orders Planned orders
Selection of transaction data types
Storage location stocks
...
Sales orders
Material Plant
Selection criteria for the transaction data
1000
... Execute
+
Save
SAP AG 2002
The transaction data transferred from the R/3 System to the APO System is defined in an integration model. The R/3 System generates this integration model (transaction CFM1). An integration model is uniquely defined by its name and application. It is useful to create several integration models with the same name, but as different applications. Ensure that the data pools of your integration models are generally not too big. This allows you to handle errors more easily. The target system you specified in the integration model determines the APO System that the transaction data is transferred into. The target system is a logical (APO) system that must have an RFC connection. The APO System determines the (R/3) target system to be used for a retransfer from APO to the R/3 System. You use a particular integration model to specify which transaction data you want to transfer. To do so, you first specify the transaction data types that are to be added to the integration model. Secondly, you specify the selection criteria that will be used to select the individual documents in the R/3 System. You complete the generation of the integration model by executing the model (this means that the data objects of the model are compiled) and then you save it.
(C) SAP AG
SCM612
7
8.8 Activate Integration Model for Transaction Data
R/3
Integration model PC
Name
Material m aster AA Material asterB Salesm order Sales order A
Target system APOCLNT800 Application
"Activate"
R/3
TD Active/Inact.
Sales order B PC
APOCLNT800
TD
Start
APO
Transaction data in APO
10:00:00
automatic Material m aster Material asterA Sales m order BA Sales order A
Incremental data transfer
Sales order A
SAP AG 2002
You must activate the integration model to transfer transaction data between R/3 and APO. You activate an integration model with the transaction Activate integration model (transaction code CFM2) in the CIF. You can have several integration models active at a time. Choose the Start function to trigger the initial data transfer. This means that the transaction data you have selected is transferred into APO for the first time. This initial transfer is usually automatically followed by the real-time link between the R/3 System and the APO System, concerning the selected transaction data. This means that once a storage location stock of a selected material changes due to a goods movement posting, the new stock is transferred into APO. In the same way, production orders that are generated in APO are immediately transferred to the R/3 System.
(C) SAP AG
SCM612
8
8.9 Publication of Planning Results
APO
Planning results in APO
For example
Delivery x
or Which R/3 System?
Collect the changes
Online transfer
R/3
Delivery x
R/3 Plant B
Plant A
SAP AG 2002
For TP/VS, there are three transactions that are used to process transfers of APO planned documents to the R/3 System: /SAPAPO/VS50 Transfer Orders to Delivery Generation /SAPAPO/VS52 Check release of Planned Orders /SAPAPO/VS51 Transmit planned Shipments to OLTP System In the Basic settings (publication of planning results) operation in APO Customizing, specify for each plant and publication type (for example, deliveries and transports (shipments) ), the R/3 System in which you are going to publish your planning results (name of the logical system). You must complete this table, even if you only operate one R/3 System. The publication process can be performed in TP/VS after the shipments have been planned and released.
(C) SAP AG
SCM612
9
8.10 Distribution Definition
Planned Shipment and Delivery Documents can be transferred fro APO to R/3 for Plant 1200:
SAP AG 2002
APO IMG: Advanced Planner and Optimizer (APO) →Basis Settings →Integration→Publication→Maintain Distribution Definition Settings in the Distribution Definition table determine which planning documents can be sent (published) to an external system, such as the R/3 System, for execution. For TP/VS, Publication Types 330 (Transport) and 340 (Deliveries) are relevant. An entry should be made in this table for all plants/DCs that have deliveries and shipment documents for execution. In addition to the Location, the Logical System to which the documents are to be transferred and the R/3 System Release must be specified. Using the Generate and Delete Distribution Definition customizing activity, multiple Distribution Definition records can be created at one time. This capability is particularly helpful if a large number of locations (plants/DCs) are involved in planning.
(C) SAP AG
SCM612
10
8.11 Transfer of Transaction Data: Unit Summary
You are now able to: Transfer of Transaction Data between the R/3 and APO Systems Initial and Incremental Transaction Data Transfer Integration Model for the Transfer of Transaction Data Publication of Delivery and Shipment Data from the APO to R/3 System s.
SAP AG 2002
(C) SAP AG
SCM612
11
8.12Exercises Unit: Transfer of Transaction Data Topic: Integration Model for Transaction Data At the conclusion of this exercise, you will be able to: 1. Create an Integration Model to transfer TP/VS-related transaction data via the CIF to APO. Transportation-relevant transactions from the R/3 System must be transferred via the CIF to APO. In addition, inventory-relevant stocks must also be transferred to APO if ATP checking is to be performed in APO. You will create an integration model to enable this transfer. 1-1
Create, generate, and activate an integration model GR## in R/3 to transfer the following transaction and inventory-relevant stocks to the target APO system: •
Sales Orders
•
Purchase Orders
•
Stock Transport Orders Stocks:
•
Storage Location
•
Special stocks with customer
•
Sales order stocks
•
Special stocks with vendor
•
Stocks in transit 1-1-1 Create the integration model: GR##. Use ‘TD’ as your Application code. Restrict your transaction data (Sales orders, purchase orders, and stock transports) selection to that data that belongs to your group number. Use the data in the following table to restrict the selection of data to your supply chain network.
(C) SAP AG
SCM612
12
Transaction Type
Data to Select
Sales orders/P.O.s/Stk Figures: Materials
T-ATC1-## T-ATD2-## T-ATD3-##
Sales orders/P.O.s/Stk Figures: Plants
10## 12## 22## 25##
Save the settings as a variant: GR##-TD 1-1-2 Generate the model. 1-1-3 Activate the model. 1-2
Record the stock balances from the ATP data in APO: 1-2-1 Product: T-ATC1-## Plant 10##
________________________________
Plant 12##
________________________________
Plant 22##
________________________________
Plant 25##
________________________________
1-2-2 Product: T-ATD2-##
(C) SAP AG
Plant 10##
________________________________
Plant 12##
________________________________
Plant 22##
________________________________
Plant 25##
________________________________
SCM612
13
1-2-3 Product: T-ATD3-##
1-3
Plant 10##
________________________________
Plant 12##
________________________________
Plant 22##
________________________________
Plant 25##
________________________________
To test the CIF interface and your integration model, you will create sales orders to be shipped from your Dresden plant to two different customers. To test the purchasing transaction transfer, you will create a purchase order from one of your vendors for materials to be received in your Hamburg plant. A stock transport order will be created to transfer stock for a material to your Paris plant. 1-3-1 Create a sales order: Order Type: OR Customer Sold-to: T-S11A## Purchase Order Number: 09-1-## Requested Delivery Date: Today + 2 weeks Material:
T-ATC1-##
50 PC
1-3-2 What plant is on the line item in sales order? _______________ 1-3-3 Record the order document number: ________________________ 1-3-4 Create a sales order: Order type: OR Customer Sold-to: T-S11B## Purchase Order Number: 09-2-## Requested Delivery Date: Today + 2 weeks Material:
T-ATC1-##
55 PC
1-3-5 What plant is on the line item in sales order? _______________ 1-3-6 Record the order document number: ________________________
(C) SAP AG
SCM612
14
1-3-7 Create a Purchase Order : Order Type: Vendor:
NB T-S11F##
Purchasing Org: Purchasing Group: Company Code:
1000 001 1000
Material: T-ATD2-## 300 PC Price: 850.00 EUR Delivery Date: In two weeks Plant: 10## Set the Confirmation Control on the line item for ANLI – Inbound delivery. 1.3.8
Record the PO Document Number: _______________________
1-3-9 Create a Stock Transport Order: Order Type: Vendor:
NB T-S100## (Intercompany Plant vendor)
Purchasing Org: Purchasing Group: Company Code:
2200 220 2200
Material: T-ATC1-##100 PC Price: 345.00 EUR Delivery Date: In two weeks Plant: 22## 1-3-10 Record the Document Number: ____________________________
(C) SAP AG
SCM612
15
Exercises Unit: Transfer of Transaction Data Topic: Customizing for Publication At the conclusion of this exercise, you will be able to: 2. Make the necessary customizing settings in APO to publish and transfer delivery and shipment document data to the R/3 Sysytem. After the transportation planning has been performed by TP/VS, the planned delivery and shipment documents are transferred to the R/3 System for the execution process.
2-1
You will make the required settings in APO to allow the transfer of planned delivery and shipment document data from APO to the R/3 System via the CIF. There are two Publication Types that are relevant for TP/VS planned documents: •
330 – Transports for shipment documents
•
340 – Deliveries for delivery documents The publication type combined with the inbound/outbound location code, the logical system and the R/3 System release number are required for each entry in the customizing table. You will need to make an entry for both publication types for each of your plants and vendors. Plants: 10##, 12##, 22##, 25## Vendors: T-S11F##, T-S11H##, T-S100## After you have created your entries in the Distribution Definition table, save the table.
(C) SAP AG
SCM612
16
8.13Solutions Unit: Transfer of Transaction Data Topic: Integration Model for Transaction Data 1-1
Create, generate and activate your Master Data Integration Model: 1-1-1 Create the integration model: R/3 SAP Standard Menu: Logistics → Central Functions → Supply Chain Planning Interface → Core Interface Advanced Planner and Optimizer → Integration Model → Generate → Create Enter Model Name:
GR##
Enter Target System: your APO logical system Enter Application:
TD
In the Add to integration model check boxes, set the following: •
Sales orders
•
POs and Preqs
•
Storage location stocks
•
Special stocks with customer
•
Sales order stocks
•
Special stocks with vendor
•
Stck in trnsit In POs and PReqs, enter your material numbers by first selecting Multple selection on the Material line. Then, in the Single vals tab enter your material numbers. Choose Copy. Iin the Plants line, choose Multiple selection and enter the plants for which to copy the material masters in the Single vals tab. Choose Copy. In Sales Orders, enter your material numbers by first selecting Multple selection button on the Material line. Then, in the Single vals tab enter your material numbers. Choose Copy. In the Plants line, choose Multiple selection and enter the plants for which to copy the material masters in the Single vals tab. Choose Copy.
(C) SAP AG
SCM612
17
In Stock figures, enter your material numbers by first selecting the Multple selection on the Material line. In the Single vals tab enter your material numbers. Choose Copy. Then, in the Plants line, choose Multiple selection and enter, in the Single vals tab, the plants for which to copy the relevant quantities. Choose Copy. Before the model is generated, you will create a Variant of the model. This variant is necessary if you want to run the model in a background process later. Choose Save. In the ABAP Variant screen, enter your variant name: GR##-TD and a description of your own choosing. Choose Save. 1-1-2 Generate the model. Choose Execute. Upon completion of the model generation, you will get a message indicating the model was generated. 1-1-3 Activate the Model. R/3 SAP Standard Menu: Logistics → Central Functions → Supply Chain Planning Interface → Core Interface Advanced Planner and Optimizer → Integration Model → Generate → Activate Enter your Model, Logical System, and APO Application code if not present in the fields. Choose Execute. Place your cursor on the line with the Date, Time, and User-ID. Select Active/Inactive. A green check mark should appear next to the line indicating that the model has been made active. Select the Start button to do the actual transfer of data to the APO system. After the transfer has been activated, you will get a confirmation message. 1-2
Record the stock balances that have been transferred from the R/3 System to APO by using the Global ATP Product Availability Report. APO SAP Menu → Global ATP → Reporting → /SAPAPO/AC03 - Product Availability 1-2-1 Enter T-ATC1-## in the Product field Enter the plant 10## in the Location field Enter A in the Business Event field. Choose Enter.
(C) SAP AG
SCM612
18
Record the stock balance from the ATP data. Repeat this process for the remaining plants/DC's. 1-2-2 Enter T-ATD2-## in the Product field. Enter the plant 10## in the Location field. Enter A in the Business Event field. Choose Enter. Record the stock balance from the ATP data. Repeat this process for the remaining plants/DCs. 1-2-3 Enter T-ATD3-## in the Product field. Enter the plant 10## in the Location field. Enter A in the Business Event field. Choose Enter. Record the stock balance from the ATP data. Repeat this process for the remaining plants/DCs. 1-3
Create sales orders, a purchase order, and a stock transport order: 1-3-1 Create a sales order: R/3 SAP Menu: Logistics → Sales and Distribution → Sales → Order → VA01 – Create Enter the Order Type: OR Choose Enter. On the next screen, enter the data from the exercise and press Enter. 1-3-2 Select the Shipping tab. Record the plant that is on the line item. 1-3-3 Choose Save. Record the document number. 1-3-4 Create the second sales order following the procedure above but using the data from Exercise section 1-3-4. 1-3-5 Record the plant that is on the line item. 1-3-6 Save the sales order and record the document number. 1-3-7 Create a Purchase Order: R/3 SAP Menu → Logistics → Materials management →Purchasing → Purchase Order → Create → ME21N - Vendor/Supplying Plant Known Order Type:
NB
Enter the Vendor Number in the Vendor field. Enter the Purchasing Org., Purchasing Group, and Company Code in the Org.data tab of the Header section. Enter the Material Number-related data in the Item Overview section. Choose Save. 1-3-8 Record the purchase order document number. 1-3-9 Create a Stock Transport order: (C) SAP AG
SCM612
19
R/3 SAP Menu → Logistics → Materials management →Purchasing → Purchase Order → Create → ME21N - Vendor/Supplying Plant Known Order Type:
NB
Enter the Vendor Number in the Vendor field. Enter the Purchasing Org., Purchasing Group, and Company Code in the Org.data tab of the Header section. Enter the Material Number-related data in the Item Overview section. Choose Save. 1-3-10 Record the purchase order document number.
(C) SAP AG
SCM612
20
Solutions Unit: Transfer of Transaction Data Topic: Customizing for Publication
2.1
Update in APO customizing the Distribution Definition table:
APO IMG: Advanced Planner and Optinizer (APO) → Basis Settings → Integration → Publication → Maintain Distribution Definition Choose the New Entries button. For each Plant/DC and Vendor, create an entry for the Publication Types 330 and 340, combined with the Logical System Number of the R/3 System. The system will insert the R/3 release. After all entries are made, Save
(C) SAP AG
SCM612
21
9 Monitoring and Error Handling
Contents: Monitoring of Application Errors Usi ng the qRFC Monitor Error Analysi s in the Application Log SCM Queue Manager Notification about Queue Blocks Using qRFC Alert Compare and Reconcile Functions to Ensure Data Consi stency in the R/3 and APO Systems
SAP AG 2002
(C) SAP AG
SCM612
1
9.2 Monitoring and Error Handling: Unit Objectives
At the conclusion of thi s uni t, you will be able to: Use the qRFC Monitor to monitor application errors Use the Application Log to perform an error analysi s Explain the concept of the SCM Queue Manager De scribe the compare and reconcile functions used to ensure data consi stency in the R/3 and APO Systems
SAP AG 2002
(C) SAP AG
SCM612
2
9.3 Monitoring and Error Handling: Business Scenario
In the event of a failure in the transferral of data between the R/3 System and APO, knowledge of the tool s that can be used to find and resolve the problem is a necessity.
SAP AG 2002
(C) SAP AG
SCM612
3
9.4 Integration Monitoring R/3
qRFC Monitor (transaction SMQ1 + SMQ2)
Application log (transaction CFG1)
APO
qRFC Monitor (transaction SMQ1 + SMQ2)
Application log (transaction /SAPAPO/C3)
Monitoring both R/3 and APO from within APO:
SCM Queue Manager (transaction /SAPAPO/CQ)
qRFC Alert (transaction /SAPAPO/CW)
Evaluation of Application log
Transaction SLQ R/3
APO
SAP AG 2002
The APO Core Interface (CIF) offers two monitoring functions to monitor the data transfer from R/3 to APO, as well as from APO to R/3; the Application log evaluation and transfer queue(s) display.
In addition, the qRFC Alert is used to monitor the outbound queues in APO and R/3 that are relevant to APO-R/3 integration. If queue blocks are detected, a message is sent to a predefined destination.
Instead of evaluating the application logs in both systems (R/3 and APO) separately when errors occur, the user can use the central SCM Queue Manager available in APO to monitor the queues and application logs in both systems.
You can find the Troubleshooting Guidelines Integration R/3 – APO on the R/3 Plug-in homepage on SAPNet (alias: R3-Plug-in) under Media Center → Literature. This document is intended to help you to localize and solve problems that arise when integrating R/3 and APO. It describes the transfer technology, the prerequisites that a data transfer must fulfill, systematic troubleshooting, the steps that must be taken when a particular error occurs, as well as how to handle special cases.
(C) SAP AG
SCM612
4
9.5 qRFC Monitor: Motivation
R/3
APO qRFC Monitor Rem ote Function Call (RFC)
Master/ Master/ Movement Movement data data
Core Core Interface Interface (Selection (Selection and and extraction extraction of of data) data)
APO transaction data
- Communication errors - Application errors Asynchronous transfer technology Rem ote Function Call (RFC)
APO ma ster/ transaction data
qRFC Monitor
live live Cache Cache
1. Buffer data 2. Transfer to target system SAP AG 2002
Usage: The communication between R/3 and APO is based on the asynchronous transfer technology of the queued Remote Function Call (qRFC). A Remote Function Call (RFC) enables calling a function module on a different server. This technology is used in the integration between APO and R/3 both for the initial data supply and incremental data transfer (from R/3 to APO) as well as for the publication of planning results (from APO to R/3).
The data is first buffered by the sending system and then transferred to the target system. The major advantage of this is that the application that triggered the data transfer does not have to wait until the update has been completed in the target system. However, this means that return parameters cannot be passed on, and potential error messages cannot be returned to the application directly.
Two types of errors are distinguished for the processing of qRFC modules: 1. Communication errors: This includes network problems, a non-existing RFC destination, and so on. Since the data transfer is repeated after certain periods, most of these communication errors should disappear once the network connection is available again. 2. Application errors: This includes program errors, failed data update in the target system, locking of objects, and missing master data for specific transaction data. Application errors cannot be solved by the system and must be handled by the system administrator.
The main instance for monitoring application errors is the qRFC Monitor. It is available both in R/3 and APO. Any queue for the target system is displayed here. Current qRFC entries can be displayed, activated, debugged, or deleted in the qRFC Monitor.
(C) SAP AG
SCM612
5
9.6 Using the qRFC Monitor (1) Example: Example:qRFC qRFCMonitor Monitor in in R/3 R/3 qRFC Monitor (Outbound queue)
R/3
Refresh
Client
Queue name
800 800
Destination
Entries
CF_ADC_LOAD APOCLNT800 3 CRM_DELT _MATERIAL IPC 3 Refresh
Client 800
Activate queue
Loc k queue
Queue name Destination CF_ADC_LOAD APOCLNT800 Refresh
Client 800 800 800
User MUSTER MUSTER MUSTER
Execut e LUW
Master data transf er
Unlock queue
3
Status 1. Date SYSFAIL 02.10.2002
... ...
Debug LUW (Logical Unit of Wor k)
Function module /SAPAPO/CIF_LOC_INBOUND /SAPAPO/CIF_PROD_INBOUN /SAPAPO/CIF_RES_ INBOUND
Status text You are not authorized to logon T ransaction recorded T ransaction recorded
Queue channel CF_ADC_LOAD = initial data transfer SAP AG 2002
During the initial data supply, transfer errors are automatically detected when an integration model is activated. A dialog box appears from which the user can navigate to the qRFC Monitor (by choosing qRFC Monitor). In addition, you can choose the Repeat and Ignore functions in the dialog box. If you choose Repeat, the system attempts to start initial data transfer again (for example, only a temporary problem in system communication). You can choose Ignore if an online transfer (for example, stocks) is stuck in the qRFC Monitor. As online transfers (for example, stocks) do not block the data channel completely, the initial data transfer can be carried out in the dialog mode, ignoring the entry in the qRFC Monitor. If, however, an earlier initial data transfer (for example, master or transaction data) has failed, it blocks further initial transfers. In this case, you must navigate to the qRFC Monitor and analyze the problem. During online transfer (for example, during stock posting in the R/3 System), transfer errors during runtime are not displayed in the dialog mode. This means that if data has not been transferred between APO and R/3, you need to check for red entries in the qRFC Monitor of the system sending the data. This check can be carried out automatically by qRFC Alert. A qRFC Monitor is available in R/3 outbound processing (transaction SMQ1) and in APO outbound processing (transaction SMQ1). By double-clicking the relevant line, all function calls for the transfer channel selected are displayed in the qRFC Monitor (you can find the INBOUND function modules available in APO in the Object Navigator, transaction SE80, under development class /sapapo/cif). The top function module blocks all following entries in the case of an error. You can display the current status text from the error short text. A detailed error message is stored in the application log of the target system. In the above example, the user from the RFC destination was either locked in APO or did not exist.
(C) SAP AG
SCM612
6
9.7 Queue Channels for Data Transfer: Example Queue channels
R/3
APO
Integration mo del X PPM f or material A, B; material A, B
(active) CF_ADC_LOAD
Integration mo del Y PPM f or material C, D, material D Initial transf er Master and transaction data
Integration mo del Z Material E
Material C
Material A Material B PPM Material A PPM Material B
(Data channel blocked)
CFMAT[mat.no.] Material A Incremental data transf er Material
Online transf er Purchase orders
Material B
APO ma ster/ transaction data
CFPO[PO number]
live live Cache Cache
(if activ e integration models exist f or materials A and B)
(if an activ e integration model exists f or purchase orders for material A)
PO number 4711 Material A PO number 4712 Material A
SAP AG 2002
In the above example, material C could not be transferred. It blocks the queue for the following data to be transferred initially (to ensure data consistency, a queue is processed sequentially). However, incremental data transfers for master data or online transfers for transaction data can still be carried out at the same time, provided that an active integration model exists for the master or transaction data in question. The following queue channels are available in the interface: Initial data transfer CF_ACD_LOAD, stocks CFSTK*, purchase orders and purchase requisitions CFPO*, planned orders/production orders CFPLO*, sales orders CFSLS*, manual reservations CFRSV*, confirmations CFCNF*, planned independent requirements CFPIR*, requirement reduction independent requirements CFMAT*, production campaigns CFPCM*, master data classes CFCLA*, master data characteristics CFCHR*, transportation CFSHP*, and planning tables CFCUVT* (in online transfers, * stands for the number of the purchase order, sales order, and so on, and in incremental data transfers of master data, for example, * stands for the material number). If only temporary communication errors occur in the network connection, the failed transfers (entry in the qRFC Monitor) can be re-started (by choosing Activate queue in the qRFC Monitor). If you only want to re-start one object type (for example, locations) within a queue, you can choose the Execute LUW function to repeat the transfer of locations. If you want to specify that the queue is automatically activated again if transfer errors occur, you can set up the RFC destination (transaction SM59) in such a way that the system makes several new attempts to transfer the data at certain time intervals. To do so, choose Destination → TRFC Options in the RFC destination and maintain, for example, the value 20 in the Connection attempts up to task field and the value 2 in the Time betw. 2 tries [mins] field. The system then makes 20 attempts in two-minute intervals to start the transfer (if no entries are made in these fields, the default setting applies, that is, 20 attempts in 15-minute intervals). If you do not want to use this function, enter X in the Suppress background job field.
(C) SAP AG
SCM612
7
9.8 Using the qRFC Monitor (2) Example: Example:qRFC qRFCMonitor Monitor in in APO APO qRFC Monitor (Outbound queue)
APO
Refresh
Client 800 800
Queue name
Destination
Entries
CFEP3040 CFIP3056
R3CLNT800 R3CLNT800
1 1
Activate queue
Refresh
Client 800
Queue name CFIP3056 Refresh
Client 800 800
User MUSTER MUSTER
Loc k queue
Destination R3CLNT 800 Execut e LUW
Planned order created in APO
Unlock queue
1
Status 1. Date SYSFAIL 02.10.2002
... ...
Debug LUW (Logical Unit of Wor k)
Function module CIF_ORDER_INBOUND_30A CIF_ORDER_INBOUND_30A
Status text No active integration model T ransaction recorded
Queue channel CFIP* = In-house production SAP AG 2002
In the example, a planned order for a finished product and purchase requisitions for the components of the finished product were created in APO. However, they were not included in any active integration model in the R/3 System at the time when the order was created in APO.
(C) SAP AG
SCM612
8
9.9 Application Log: Motivation
R/3
APO
Application log R/3: Error
RFC
Master/ Master/ transaction transaction data data
Core Core Interface Interface
- Communication errors - Application errors
APO ma ster/ transaction data
RFC Application log APO: Error
live live Cache Cache
SAP AG 2002
Display entries: You can use the application log to trace when (time), and what (data objects and integration model) was transferred by whom (user). In addition, the application log provides a detailed error message if an application error occurred. As a prerequisite, logging must have been switched on. If errors occurred during transfers, detailed error messages are stored in the application log of the target system. Prerequisite: Logging mode switched on (transaction CFC2 in R/3 and /SAPAPO/C4 in APO; you can make settings as required under Logging). Normal (only the number of data records transferred is logged) Detailed (the number and content of the data records transferred is logged): Detailed logging can easily lead to large database tables and decreased performance when used in a productive system. For this reason, we recommend using detailed logging only when the data is needed (for example, in the implementation phase). Delete entries: You can delete logs of the application log in R/3 and APO. The system does not delete the logs automatically. To prevent extreme database load, we recommend deleting the logs periodically. If you want, you can schedule background processing. If you do not make an entry in the date and time fields, all logs older than two weeks are deleted automatically.
(C) SAP AG
SCM612
9
9.10 Using the Application Log (1) Example: Example:Application Application Log Log in in R/3 R/3 qRFC Monitor Refresh R/3 Client 800 800
User MUST ER MUST ER
Function module Status text /SAPAPO/CIF_T PSRC_INBOU Loc. 0000001003 does not exist /SAPAPO/CIF_GEN_EVENT Transaction recorded
R/3 Application Log Date
User
02.10.2002 MUSTER
Number
Subobject type
530
Initial data supply
Function: CIF_LOCAT ION_SEND: Plant 1000
APO Application Log Date
User
Number
Subobject type
02.10.2002 USERADMIN 4 Sources of supply Problem class: very important Problem class: medium Problem class: additional information Location 0000001003 does not exist
SAP AG 2002
In the example, an initial data supply was carried out in the R/3 System to transfer several different master data, including purchasing info records. One of the purchasing info records transferred was for a vendor that does not exist in APO. Message display: You can select different subobjects for the CIF object in the R/3 and APO application log. These include, EP External procurement (inbound), IP In-house production (inbound), or INITIAL Initial supply and LOCATION Location: customer, plant, vendor (for performance reasons, the entries for an initial supply and an incremental data transfer are grouped under the subobject INITIAL). For more subobjects, choose F4 for the Subobject field on the initial screen of the application log. By double-clicking on a subobject, you can navigate to Messages for the relevant transfer log. This provides an overview of the data objects that have been sent between the systems. This function is particularly helpful when determining errors. qRFC Monitor: The transaction ID of the sending application serves as the key of an error message (TID field in the qRFC line of the qRFC Monitor of the sending system). When you enter this number, you can display all messages for this qRFC call in the target system. In the application log, you enter the number of the transaction ID in the Ext. identif. field and execute the selection. The system displays all messages for the call in question.
(C) SAP AG
SCM612
10
9.11 Using the Application Log (2) Example: Example:Application Application Log Log in in APO APO APO qRFC Refresh Monitor Client 800 800
User
Function module
Status text
MUSTER MUSTER
CIF_ORDER_INBOUND_30A CIF_ORDER_INBOUND_30A
No active integration model T ransaction recorded
APO Application Log Date
User
02.10.2002 MUST ER
Number
Subobject type
120
In-house production
Function: /SAPAPO/CIF_IP_OUTBOUND: Order material P-102, plant 1000
R/3 Application Log Date
User
Number
Subobject type
02.10.2002 USERADMIN 1 In-house production Problem class: very important Problem class: medium Problem class: additional information Inbound R3CLNT800: For system APOCLNT800 no active integration model for type T_PLO filter object P-102 1000 SAP AG 2002
In the example, a planned order for a finished product and purchase requisitions for the components of the finished product have been created in APO. However, they were not included in any active integration model in the R/3 System at the time when the order was created in APO. Therefore, the orders were not created in R/3, but kept in the queue. In the outbound log, you always recognize the log of successful transfers. In the logging of the target system, error messages are displayed if errors occurred during transfers.
(C) SAP AG
SCM612
11
9.12 SCM Queue Manager (1)
APO
R/3
Execute
SCM Queue Manager Systems
Expand nodes Systems R3CLNT800 Object types
APO outbound types EP Plug-in outbound types T_INITIAL EP Ext. Procurement T_INITIAL Initial trans. IP In-House Production T_ORD Planned ords,.. ... ...
R/3
RFC
APO
- Communication errors - Application errors RFC SAP AG 2002
Instead of separately evaluating the application logs in both systems (R/3 and APO) when errors occur, the user can use the central SCM Queue Manager available in APO (transaction /n/SAPAPO/CQ) to monitor the queues and application logs in both systems.
(C) SAP AG
SCM612
12
9.13 SCM Queue Manager (2) APOCLNT800
External procurement In-house production Planned ind. reqmnts Planning f ile entries Production campaigns Sales order Transportation Delivery Reservations ...
System : APOCLNT800 Type: In-house production Refresh
Queue
Appl.log
Destination Error text
CFIP3056 R3CLNT 800
User
No active integration MUST ER model
Date ...
R3CLNT800
Initial supply Purchase orders Planned orders Production orders Sales orders Planned ind. requirements. Manual reservations Production campaigns Confirmations Transportations Stocks Characteristics Classes
R32CLNT800
Initial data supply...
SAP AG 2002
(C) SAP AG
SCM612
13
9.14 qRFC Monitoring: Notification about Exception Messages (1)
R/3
APO RFC
Master/ Master/ Movement Movement data data
Core Core Interface Interface
- Communication errors - Application errors APO APO ma master/ ster/ transaction transaction data data
RFC Mail to initiator or adm inistrator
live live Cache Cache
SAP AG 2002
Usage: Application errors that occur during data transfer are not reported directly to the user because data transfer between APO and R/3 is asynchronous. Instead, the qRFC entries block the outbound queue. Any subsequent data transfers cannot pass the outbound queue. By monitoring the qRFC exception message, queue blocks are detected and the following are notified: •The initiator of the block via SAPOffice Inbox Mail (the initiator of every queue block receives a message stating that he or she has caused a block) •The administrator, via SAP Office Inbox or an Internet mail (one person is chosen to receive all messages). If you want to send the messages to an e-mail address, you must make the necessary settings in SAPconnect (Transaction /SCOT).
Features: The report (transaction /N/SAPAPO/CW) monitors all APO outbound queues, and the queues of the logical R/3 Systems connected to APO. Depending on the settings on the selection screen, local qRFC-API modules in the APO system, or qRFC-API (Application Program Interface) modules in the connected R/3 System, or both are called up synchronously and the status of the relevant outbound queues is queried. You can find out the names of the relevant logical systems from the selection screen entries, and from the entries in the /SAPAPO/SYSDIR table (to maintain, use /SAPAPO/C2).
If the system recognizes queue errors or blocks, a message is generated from the status information. The message is sent via the SAPOffice API to the relevant destination(s) or administrator(s), provided the settings are made accordingly. In addition, the list of all incorrect outbound queries is output in list form.
(C) SAP AG
SCM612
14
9.15 qRFC Monitoring: Notification about Exception Messages (2)
R/3
APO
Execute
qRFC M onitoring Local outbound queues
Target systems * Local queue names CF* Queue errors only Notification
No To initiator To administrator
MUSTER
B
Remote outbound queues
Remote systems Destinations Remote queue names CF* Queue errors only (remote system) Notification
...
SAP AG 2002
Local outbound queues: 1. Enter the target system (logical system). You can use placeholders. 2. Enter the name of the queue to be monitored. 3. (Queue errors only indicator). Specify whether you want the monitor to only find real application errors (SYSFAIL) (indicator set) temporary errors, such as communication errors (CPICERR), or errors caused by temporary application locks (indicator not set). 4. Specify where the message is to be sent: No notification (the message is not sent and is only displayed), To initiator (the message is sent to the initiator of the block), To administrator (all messages are sent to one person): You can change the entry in the address field (the current user is set as the default value). 5. Choose a recipient type. The recipient type determines the message format. You can now choose between B (SAP user) and U (Internet address). If you choose recipient type U, ensure that you make the relevant entries in SAPconnect. 6. Execute the report program. The message is sent or displayed on the screen.
Remote outbound queues: In the Remote outbound queue groupbox, you define the settings for monitoring the outbound queues of connected R/3 Systems: 1. In the Remote systems field, enter the name of the RFC destinations whose outbound queues you want to monitor. You may use wildcards (for example SX*). If you do not enter anything, none of the outbound queues of the connected systems are monitored. 2. In the Destinations in the remote system field, enter the name of the target systems called in the remote system (usually the APO system itself). You may use wildcards (for example SX*). 3. In the Remote queue name field, enter the names of the R/3 outbound queues to be examined in the remote systems to be monitored. All R/3 outbound queues that are addressed via the APO CIF integration have CF as the prefix. 4. All other entries are made in the same way as for local outbound queues. If you want to run the qRFC Alert periodically, you must schedule the report via the SAP job definition (transaction SM37).
(C) SAP AG
SCM612
15
9.16 Compare/Reconcile Function for Data Inconsistencies in R/3 and APO: Compare
APO
R/3
Report /SAPAPO/CIF_DELTAREPORT2 Partner system (R/3) R3CLNT800 Material
P-102
(optional)
Plant
100
(optional)
Integration model
Pump
(optional)
Objects to be checked
Sales orders Production/process orders Purchase requisition ... ... Storage location stocks Sales order stocks ... ... Database
Compare
live Cache
SAP AG 2002
Usage: Data inconsistencies between APO and R/3 can arise in certain circumstances (for example, due to application errors or manual deletion of queue entries). The compare/reconcile function helps you to identify and correct such data inconsistencies. In APO, the function covers the following objects: Stock, sales order, planned order, production order, purchase order, and purchase requisition. When you use the compare/reconcile function, the system performs a comparison and lists any inconsistent objects it identifies. Then you can select individual, several, or all objects for the reconcile function. The selected data can be sent from R/3 to APO. Procedure: Start report program /SAPAPO/CIF_DELTAREPORT2 in the ABAP Editor of APO (transaction SE38). Choose the R/3 System in the Partner system field. In addition, you can restrict the compare/reconcile function to certain products, locations, integration models, or stocks and transaction data by entering selection parameters, and therefore reducing the runtime of the transaction. After the report has been executed, an overview of the results of the comparison is shown on the next output screen, separated according to orders and stocks. A line with the following information is displayed for every object type checked: Total (total number of R/3 objects selected for comparison), Errors (total number of errors found), All other columns: (distribution of the errors to individual error areas). You can run the DELTAREPORT also with Transaction /SAPAPO/CCR or report /SAPAPO/CIF_DELTAREPORT3. This Deltareport is available from Release 3.1. You can downgrade it for Release 3.0 by starting with Support Pack 19.
(C) SAP AG
SCM612
16
9.17 Compare/Reconcile Function for Data Inconsistencies in R/3 and APO: Reconcile
APO
R/3
Execute
Report results list Results
Sales orders
Deviations in APO Send to APO Sent
Material
Storage Plant location Stock
P-102
1000
0002
11
Quantity APO 10 Documents
Storage loc. stocks
Reason ...
Sales orders Production/process orders ... Supplies
Storage location stocks ...
Database
Reconcile
live Cache
SAP AG 2002
(C) SAP AG
SCM612
17
9.18 Monitoring and Error Handling: Unit Summary
You are now able to: Use the qRFC Monitor to monitor application errors Use the Application Log to perform an error analysi s Explain the concept of the SCM Queue Manager De scribe the compare and reconcile functions used to to ensure data consi stency in the R/3 and APO System s
SAP AG 2002
(C) SAP AG
SCM612
18
10 Vehicle Scheduling (VS): Basic Settings
Contents: Configuration and Customization Activities
SAP AG 2002
(C) SAP AG
SCM612
1
10.2 Vehicle Scheduling (VS): Basic Settings: Unit Objectives
At the conclusion of thi s uni t, you will be able to: Understand activitie s required to configure the TP/VS system
SAP AG 2002
(C) SAP AG
SCM612
2
10.3 Vehicle Scheduling (VS): Basic Settings: Business Scenario
In preparation for running the TP/VS modeling and optimization process, the planning environment is establi shed by making various customizing settings and creating the necessary master data in TP/VS.
SAP AG 2002
(C) SAP AG
SCM612
3
10.4 Vehicle Scheduling Process Flow (1) Configuration
Master Data
Modeling
Optimization (Load Consolidation & Vehicle Schedul ing)
Create/Transfer Shipments
Backorder Processing
Create/Transfer Deliveries
Carrier Selection
Carrier Tendering
Release Shipments
SAP AG 2002
(C) SAP AG
SCM612
4
10.5 VS General Customizing Activities Basic Settings
Carrier Selection
Geocoding
Number Ranges
Determine Shipment Types
Transportation Modes
Transportation Groups
Transportation Methods/Vehicles
Freight Units
Carrier Profile
Interfaces (R/3 Related)
Assignment of Transportation Zone to Locations
Field Mapping of Communication Structures
Backorder Processing
Optim ization
Profiles (Optimization/Cost)
Transportation Methods and Groups Compatibility
Transportation Groups Compatibility
Transportation Methods and Locations Compatibility
Definition of Dimension Units
Filters
Sort Profiles
Scheduling
SAP AG 2002
APO IMG: Advanced Planner and Optimizer (APO) →Transportation Planning/Vehicle Scheduling (TP/VS)
(C) SAP AG
SCM612
5
10.6 Order of Maintenance 1. Creation of Master Data in R/3 2. Creation of Integration Models and the transfer of Master Data R/3 → APO
Plants, DCs
Customers
Suppliers
Carriers
Materials
Locations
Products
3. Creation of Transportation Groups 4. Creation of Transportation Modes 5. Creation of Transport Methods 6. Creation of Vehicle Resources and assignment to active model 000 7. Modeling in Supply Chain Engineer 8. Creation of Transportation Lanes 9. Assignment of Transport Methods to Transportation Lanes 10. Assignment of Carriers to Lanes and Transport Methods
SAP AG 2002
(C) SAP AG
SCM612
6
10.7 Geocoding
Geocoding Table (APO IMG)
APO Location Master Record SAP AG 2002
Geocoding enables the system to assign longitude and latitude coordinates to the various locations in APO. These coordinates are used to estimate distances between locations. The geocoding program supplied by the SAP System determines the longitude and latitude based on the Country and Region codes. the steps required to install third-party geocoding programs are included in the APO IMG customizing activities. Customizing settings allows the geocoding program(s) to be assigned at the Country code level.
(C) SAP AG
SCM612
7
10.8 TP/VS Number Ranges APO IMG: Advanced Planner and Optim izer→Transportation Planning/Vehicle Scheduling (TP/VS) →Basic Settings
→Define Number Range for Temporary Shipments
→Define Number Range for Shipments
SAP AG 2002
The temporary shipment number range is used to assign shipment numbers to shipment documents created during the Route Optimization process. The Number Range for Shipments table is used to assign shipment numbers to shipment documents that have been released to the R/3 System. This number range MUST match the number range assignment in the R/3 System for External Number assignment.
(C) SAP AG
SCM612
8
10.9 Transportation Mode, Transportation Method, Resources
Transp. Mode
For example, Truck, Rail, Air, Ship, and so on
For example, FTL, LTL, Parcel Service, Barge, and so on
Transportation Method
For example, Maintenance of capacities,depot locations, and so on,for individual vehicles
Vehicle Re source s
SAP AG 2002
Transportation Mode: APO IMG: Advanced Planner and Optimizer (APO) →Transportation Planning/Vehicle Scheduling (TP/VS) → Basic Settings →Maintain Transportation Mode The Transportation Mode is a code defined to indicate the actual ‘mode’ of transportation. This code is assigned to the Transport Method. The Transportation Mode in TP/VS should correspond to the Transportation Mode used in the R/3 System (R/3 IMG: Logistics Execution→Transportation→Basic Transportation Functions→Routes→Define Routes→Define Modes of Transport). Transport Method: APO IMG: Advanced Planner and Optimizer (APO) →Supply Chain Engineer (SCE) → Maintain Transport Method The Transport Method is used to identify a method of transportation (for example, a 48’ truck with full truck load capacity or refrigerated truck). The Transportation Methods are assigned to Vehicle Resources in APO master data. In addition, the Transport Methods will be assigned to Transportation Lanes. Vehicle Resources APO SAP Menu: Master Data→Resource Vehicle Resources are used to represent a unit of transportation and its capacity and planning parameters. A Vehicle Resource is independent of a particular carrier.
(C) SAP AG
SCM612
9
10.10 Transportation Groups R/3
APO
SAP AG 2002
The Transportation Group is used to categorize materials according to their transportation requirements. Like materials in the R/3 System, each APO Product is assigned to a Transportation Group code. A product attribut for grouping could be refrigerated transportation required or dangerous goods. The Transportation Group codes in APO should match the R/3 Transportation Group codes. APO IMG: Advanced Planner and Optimizer (APO) →Transportation Planning/ Vehicle Scheduling (TP/VS) → Basic Settings → Maintain Transportation Group R/3 IMG: Logistics Execution → Transportation → Basic Transportation Functions → Routes → Route Determination → Define Transportation Groups
(C) SAP AG
SCM612
10
10.11 Freight Units
SAP AG 2002
APO IMG: Advanced Planner and Optimizer (APO) →Transportation Planning/Vehicle Scheduling (TP/VS) →Basic Settings→Define Freight Units Sales Order Consolidation: • This features allows for uniform schedule lines to be consolidated into one transport unit (restricts the amount of data the optimizer has and gives greater clarity to the Interactive Planning Board). For consolidation of sales orders, the following conditions must be met: - The order items have the same goods recipient and the same desired delivery date - All order items have the same transport group - If this is not the case, individual transport units are created for all items or schedule lines - Total items of an order per unit do not exceed the upper consolidation limit, maintained in the TP/VS Optimizer in APO Customizing under Defining dimensions/units - If any of these criteria is not fulfilled, no consolidation occurs and the individual order items become individual transport units Planning of ATP Confirmed Dates or Required Dates: • This feature allows you to choose the date to use for optimization; the ATP confirmed date or the desired delivery date. (Note: Choosing the ATP Confirmed Date is not compatible with the Order Consolidation feature)
(C) SAP AG
SCM612
11
10.12 Determine Shipment Type
R/3 Shipment Type
SAP AG 2002
APO IMG: Advanced Planner and Optimizer (APO) →Transportation Planning/Vehicle Scheduling (TP/VS) →Interfaces→Determine Shipment Type This customizing activity is used to map the Transportation Method and Inbound/Outbound Shipment to the corresponding Shipment Type in the specified Logical System where the planned shipment documents are to be transferred. The Shipment Types(Vehicle Column) must be defined in the R/3 System for the transfer of the shipment to take place. R/3 Shipment Type can be found : R/3 IMG: Logistics Execution →Transportation → Shipments → Define Shipment Types
(C) SAP AG
SCM612
12
10.13 Transportation Matrix, Used for Deadheads
Point A Plant
Point B Customer
Point D Plant
= Loaded Trip = Deadhead = Continued route
SAP AG 2002
APO IMG: Advanced Planner and Optimizer (APO) → Transportation Planning/Vehicle Scheduling (TP/VS) → Basic Settings→ Maintain Transportation Matrix This customizing activity is used for private fleet vehicles and is not required for TP/VS for Route Optimization and Scheduling. This activity indicates that a vehicle is not available immediately after a shipment has been delivered, since the vehicle needs a certain amount of return time or time to reach the next loading point. Example: A shipment is transported from departure point A to destination B. Loading occurs at point A. While it is on the way from A to B, this vehicle is not available for scheduling (the resource is in use). Once the shipment has been delivered to point B, the resource is still not available, since it must first return to point A to be loaded again. Therefore, the resource vehicle is in use for the following routes: Transportation lane: A → B Dead-heading: B → A or Continued route: B → D Available again: as of point A or D
A Transportation Matrix is not used for an APO3.0 SP21 or greater or APO3.1 system.
(C) SAP AG
SCM612
13
10.14 How to maintain a Transportation Matrix
SAP AG 2002
Standard Settings: You have maintained the corresponding transportation lanes and transportation times in the Supply Chain Engineer. Activities: Enter the vehicle key on the Transfer the Distance Matrix for Vehicles into the liveCache screen. The liveCache uses the transportation times that were maintained in the Supply Chain Engineer (Transportation Method) as a basis for calculating the empty run (deadheading) from the destination point to the departure point. It is not necessary to maintain a transportation matrix starting with Support Package 20.
(C) SAP AG
SCM612
14
10.15 Vehicle Scheduling (VS): Basic Settings: Unit Summary
You are now able to: Understand activitie s required to configure the TP/VS system
SAP AG 2002
(C) SAP AG
SCM612
15
10.16Exercises Unit: Vehicle Scheduling (VS): Basic Settings Topic: Transportation Methods and Resources At the conclusion of this exercise, you will be able to: •
Update the APO IMG with Transportation Methods (Vehicles).
•
Navigate to the Transportation Mode and Group customizing tables in the APO IMG.
•
Create Resources in APO Master data and assign them to your supply chain network using the Supply Chain Engineer.
Before TP/VS can be used for planning, various customizing settings must be completed to create the relationship between the various modes of transportation that will be used to transport shipments, the transportation methods that relate the speed and working time availability of a given type of vehicle and the capacity constraints of individual vehicle resources. 1-1
Review the settings in the Transportation Mode table in APO Customizing. 1-1-1 List the Transportation Modes that exist in the table: ______________________ ______________________ ______________________ ______________________
(C) SAP AG
SCM612
16
1-2
Create two new transportation methods (vehicles) that you will use in your TP/VS environment: 1-2-1 Create Transportation Method FTL## with the following settings: Description: AverageSp: Factor: Work Time: Component:
FTL – Gr. ## 80 1.200 24:00 Compatible with all
TranspMode: FTL OwnTrMeth: blank Schedule: blank 1-2-2 Create Transportation Method: LTL## with the following settings: Description : AverageSp: Factor: Work Time: Component: TranspMode: OwnTrMeth: Schedule:
LTL – Gr. ## 60 1.400 24:00 Compatible with all LTL blank blank
1-2-3 Save the table. 1-3
Create a Vehicle Resource with the following characteristics: Resource: G##-FTRK01 Location: leave blank (This resource will be valid for all locations) Planner: leave blank Resource Category: T Choose the Create button. In the Create Resources Header Data screen, select the Vehicle tab and enter the following data on the resource line: Location: Leave blank Vehicle: FTL## Time zone: CET Dimension: Mass Factory Calendar: W8 Start: 00:00:00 End: 23:59:00 Capacity: 18000 Unit of Measure: KG Finite Scheduling:
Select
Choose Enter. Select the Standard Capacity tab. Create an addition dimension: Volume of 150 M3 Choose Save. (C) SAP AG
SCM612
17
1-4 Create four additional vehicle resources with characteristics identical to the one you just created: G##-FTRK01. They should have Vehicle Resource Numbers of G##FTRK02, G##-FTRK03, G##-FTRK04 and G##-FTRK05. Use the resource Copy function to create these. 1-5 Create a Vehicle Resource: G##-LTRK01 with the following characteristics: Resource: G##-LTRK01 Location: leave blank (This resource will be valid for all locations) Planner: leave blank Resource Category: T Choose the Create button. In the Create Resources Header Data screen, select the Vehicle tab and enter the following data on the resource line: Location: Leave blank Vehicle: LTL## Time zone: CET Dimension: Mass Factory Calendar: W8 Start: 00:00:00 End: 23:59:00 Capacity: 9000 Unit of Measure: KG Finite Scheduling: Select Choose Enter. Select the Standard Capacity tab. Create an addition dimension: Volume of 75 M3 Choose Save. 1-6 Create four additional vehicle resources with characteristics identical to the one you just created: G##-LTRK01. They should have Vehicle Resource Numbers of G##LTRK02, G##-LTRK03, G##-LTRK04 and G##-LTRK05. Use the resource Copy function to create these. 1-7
Select and assign your new vehicle resources to your SCE work area: Model: 000 Work Area: GR## Transportation Resources: G##-FTRK01 through G##-FTRK05 and G##-LTRK01 through G##-LTRK05. After assigning the resources, Choose Save.
(C) SAP AG
SCM612
18
Exercises Unit: Vehicle Scheduling (VS): Basic Settings Topic: Transportation Lane Creation At the conclusion of this exercise, you will be able to: •
Create and maintain transportation lanes individually and using the mass maintenance function.
The transportation lane represents the path that transportation shipments follow to move merchandise between a source (plant/DC, Vendor) and a target location (customer, plant/DC). Associated with the transportation lanes are the transportation methods. A critical step in establishing the necessary master data for TP/VS planning is creation of the transportation lanes. 2-1
Create a pair of transportation lanes between your two plants: 2-1-1 Create the transportation lane from plant 10## to 12##. 2-1-2 Assign to these two lanes the transportation methods you have created: FTL## and LTL##. 2-1-3 In the Product Procurement section of the transportation lane, select All Products. The validity periods for all objects related to the transportation lanes should be: Start date is today's date, the End date should be: 12/31/9999. 2-1-4 Assign to the lane the transportation methods you have created: FTL## and LTL##. Perform the Generate proposal process to have the system calculate the distance between the plants automatically. Assign a cost of 1.000 per KM as the transportation cost. 2-1-5 Choose Save. 2-1-6 Create a second transportation lane: from plant 12## to 10##. For this lane assign a transportation cost of 1.200 per KM.
(C) SAP AG
SCM612
19
2-2 Using the Mass Creation of Transportation Lanes function create the following transportation lanes based on the transportation lane from 10## to 12##. 2-2-1 Source 12##
Target T-S11A## T-S22A## T-S33A## T-S11B## T-S11C##
2-2-2 Source
2-3
(C) SAP AG
Target
T-S11F##
10##
T-S11H##
10##
After creating the transportation lanes, display them to verify that both transportation methods have been assigned to each lane. Use the Supply Chain Engineer to do this check. In addition, delete the circular lanes created during the mass transportation lane creation process.
SCM612
20
Exercises Unit: Vehicle Scheduling (VS): Basic Settings Topic: Shipment Type Determination At the conclusion of this exercise, you will be able to: •
Make the required settings in APO customizing to determine the R/3 Transportation Shipment Types.
After shipments are planned in TP/VS, they will be "published" and transferred to the R/3 System for execution. A shipment type must be determined for the process to work properly. You will make the required setting for the assignment of the R/3 shipment types. 3.1
(C) SAP AG
Update the Shipment Type determination table to assign the Shipment Types you created in the R/3 System, AI## and AO##. 3.1.1
Create an entry in the Shipment Type Determination table for each of your Transportation Methods, FTL## and LTL##, for the Shipment Types AI## and AO##. Use the Logical System Number of the R/3 System.
3.1.2
Choose Save.
SCM612
21
Exercises Unit: Vehicle Scheduling (VS): Basic Settings Topic: Mapping Table for Vehicles At the conclusion of this exercise, you will be able to: •
Perform the APO customizing required to map the Transportation Methods to the corresponding Packaging Material that represent the Methods of Transport in R/3.
Your business processes include packing materials from the deliveries into handling units that will be packed into the method of transportation. To facilitate this you want the shipment documents to include a packaging material that represents the trailer, container, or other unit of transportation. To have the packaging material created automatically when the shipment document is transferred to R/3 you will have to update the Mapping Table for Vehicles. 4-1
Create an entry in the Mapping Table for Vehicles for the packaging materials created in R/3, FTL-## and LTL-##, that represent the transportation methods FTL## and LTL##, respectively. Note: The alphabetic characters in the material number in the ExtVehDesc field must be entered in all capital letters.
(C) SAP AG
SCM612
22
10.17Solutions Unit: Vehicle Scheduling (VS): Basic Settings Topic: Transportation Methods and Resources 1-1
Display the Transportation Mode table: APO Customizing → Advanced Planner and Optimizer (APO) → Transportation Planning/Vehicle Scheduling (TP/VS) → Basic Settings → Maintain Transportation Mode 1-1-1 List the transportation modes shown in the table.
1-2
Create the new transportation methods: APO Customizing → Advanced Planner and Optimizer (APO) → Supply Chain Engineer (SCE) → Maintain Transport Method 1-2-1 Create the first Transportation Method by selecting the New Entries Enter FTL## in Vehicle field. Enter the remainder of the data as specified in the exercise. 1-2-2 Enter LTL## in the Vehicle field. Enter the remainder of the data as specified in the exercise. 1-2-3 Choose Save.
1-3
Create a Vehicle Resource, G##-FTRK01: APO SAP Menu → Master Data → Resource Resource: G##-FTRK01 Location: leave blank (This resource will be valid for all locations) Planner: leave blank Resource Category: T Choose the Create button. In the Create Resources Header Data screen, select the Vehicle tab and enter the remaining data as indicated in the exercise and Save the record.
(C) SAP AG
SCM612
23
1-4
Create four additional Vehicle Resources using the Copy function: Enter: Resource: G##-FTRK01 Location: Leave blank Resource Category: T Select the Change Resource button. Select the Resource line with G##-FTRK01. Select the "Copy Resources" button. Select Replicate all Selected Resources . Enter 2 in the Start number field. Enter 4 in the Number of resources field. Change the New Resource Entry field by removing the last digit of the resource. It should look like G##-FTRK0 after the change. Select Copy Object. Choose Save. Choose Back.
1-5
Create Vehicle Resource, G##-LTRK01. APO SAP Menu → Master Data → Resource Resource: G##-LTRK01 Location: leave blank (This resource will be valid for all locations) Planner: leave blank Resource Category: T Choose the Create button. In the Create Resources Header Data screen, select the Vehicle tab and enter the data as indicated in the exercise and Save the record.
(C) SAP AG
SCM612
24
1-6
Create four additional Vehicle Resources using the Copy function: Enter: Resource: G##-LTRK01 Location: Leave blank Resource Category: T Select the Change Resource button. Select the Resource line with G##-LTRK01. Select the Copy Resources button. Select the Replicate all Selected Resources Enter 2 in the Start number field. Enter 4 in the Number of resources field. Change the New Resource Entryfield by removing the last digit of the resource. It should look like G##-LTRK0 after the change. Select the Copy Object. Choose Save. Choose Back.
1-7
Update your SCE work area to include your new vehicle resources: APO SAP Menu → Master Data → Supply Chain Engineer → Maintain Model Enter:
Model: 000 Work Area: GR##
Select the Change Model button. Choose the Resources tab. Choose the Transport resources title field. Right-click on the Transport resources title field. Select Add Objects to Work Area. In the pop-up window, enter G##-FTRK01 and G##-FTRK05 in the two Internal char. value fields on the first line. Enter G##-LTRK01 and G##-LTRK05 in the two Internal char. value fields on the second line. Select the Copy button. (green check mark). The vehicle resources will not appear under the Transport resources heading. Select all of your resources in the list by mouse-clicking on the first resource and then shift mouse-click on the remaining resources. Right mouse-click on the selected resources. Select Add to model. Choose Continue when the pop-up box displays. Choose Save.
(C) SAP AG
SCM612
25
Solutions Unit: Vehicle Scheduling (VS): Basic Settings Topic: Transportation Lane Creation 2-1
Create the transportation lanes from Plant 10## to Plant 12## and from Plant 12## to Plant 10##: APO SAP Menu → Master data → Transportation Lanes 2-1-1 Enter the following: Model:
000
Source loc.:
10##
Target loc.:
12##
Select the Create button. 2-1-2 In the Product Procurement section of the screen, select the Creation of a new entry icon. When the Product procurement entry box opens: Select All products. Enter today's date in the Start date field. Enter 12/31/9999 in the End date field. Select Copy and close (the green check mark). 2-1-3 In the Means of trans section, select the Creation of a new entry icon. When the Transportation method entry box opens: Enter FTL## in the Transport method field. Enter today's date in the Start date field. Enter 12/31/9999 in the End date field. De-select the Aggr. planning option. Select the Generate proposal button. After the distance is calculated, enter 1.000 in the TranMethods Costs field. Select the Copy icon (it's the middle one at the top of the box).
(C) SAP AG
SCM612
26
2-1-4 Create a second Means of Trans : Enter FTL## in the Transport method field. Enter today's date in the Start date field. Enter 12/31/9999 in the End date field. De-select the Aggr. planning option. Select the Generate proposal button. After the distance is calculated, enter 1.000 in the TranMethods Costs field. Select the Copy and close icon (it's the green check mark at the top of the box). 21-5
Choose Save.
2-1-6 Create the second transportation lane: Model:
000
Source loc.:
12##
Target loc.:
10##
Select the Create button. Perform the same procedure as outline in sections 2-1-2 through 2-1-5 above, except enter 1.200 as the TranMethods Costs. 2-2
Create the remaining transportation lanes using the Mass Creation of Transportation Lanes function: APO SAP Menu → Master data → Mass Creation of Transportation Lanes 2-2-1 Create the transportation lanes using the following: Copy from:
Source:
Target:
10##
12##
Creation of transportation lanes between locations: Source:
12##
Target:
T-S11A##
T-S22A## T-S33A## T-S11B## T-S11C## (Use the Multiple Selection function to enter the list of Target locations) Select Execute. When the dialog box pops up asking if you want to continue and displays the number of lanes to be created (there should be 5), select Y. 2-2-2 Create the transportation lanes between the Vendors and Plant 10## and create the return lanes: Create the transportation lanes using the following: Copy from: (C) SAP AG
Source:
10## SCM612
27
Target:
12##
Creation of transportation lanes between locations: Source:
T-S11F##
10## Target:
10##
T-S11F## Select the Execute button. When the dialog box pops up asking if you want to continue and displays the number of lanes to be created (there should be 4), select Y. Why are there four lanes? _____________________________ __________________________________________________ __________________________________________________ Create the lanes between Vendor T-S11H## and Plant 10##: Copy from:
Source:
Target:
10##
12##
Creation of transportation lanes between locations: Source:
T-S11H##
10## Target:
10##
T-S11H## Select the Execute button. When the dialog box pops up asking if you want to continue and displays the number of lanes to be created (there should be four), select Y.
(C) SAP AG
SCM612
28
2-3
Check your Work Area in the Supply Chain Engineer to make sure the lanes were created properly: APO SAP Menu → Master Data → Supply Chain Engineer → Maintain Model Model:
000
Work Area:
GR##
Select the Change button. Use the Zoom in icon to display, with clarity, the transportation lanes attached to your Vendors: T-S11F## and later, T-S11H##. Notice the single arrowhead attached to Vendor T-S11F##. This is the lane that was created during the mass creation of the lanes. You will delete it as follows: Place your cursor on the arrowhead. A box should pop up identifying the lane: TS11F## - T-S11F##. Right-click. In the popup box select Delete. In the Confirm deletion popup box, select Yes. Delete the second circular lane created for Vendor T-S11H##. Choose Save.
(C) SAP AG
SCM612
29
Solutions Unit: Vehicle Scheduling (VS): Basic Settings Topic: Shipment Type Determination
3-1
Update the Shipment Type Determination table to assign your R/3 System shipment types: APO IMG: Advanced Planner and Optimizer (APO) → Transportation Planning/Vehicle Scheduling (TP/VS) → Interfaces → Determine Shipment Type 3-1-1 Select New Entries button. Enter FTL## in the Trsp.Meth field. Enter the R/3 Logical System Number. Select I Inbound in the In/outbound Shipment field. Enter AI## in the Vehicle field. On the next line, repeat the process but: Select O Outbound in the In/outbound Shipment field and Enter AO## in the Vehicle field. Create two more lines in the table using the same steps as above but with Transportation Method LTL## 3-1-2 Choose Save.
(C) SAP AG
SCM612
30
Solutions Unit: Vehicle Scheduling (VS): Basic Settings Topic: Mapping Table for Vehicles 4-1
Create the entries in the Mapping Table for Vehicles: APO IMG: Advanced Planner and Optimizer (APO) → Transportation Planning/Vehicle Scheduling (TP/VS) → Interfaces → Maintain Mapping Table for Vehicles Select the New Entries button. Enter FTL-## (must use capital letters) in the ExtVehDesc field. Select the Logical System Number of the R/3 System. Enter FTL## in the Vehicle field. On the next line: Enter LTL-## (must use capital letters) in the ExtVehDesc field. Select the Logical System Number of the R/3 System. Enter LTL## in the Vehicle field. Choose Save.
(C) SAP AG
SCM612
31
11 Vehicle Scheduling (VS)
Contents: The optimization process flow in TP/VS The VS Optimizer Creating the Cost Profile Creating the VS Alert Profile Creating the Optimization Profile Interactive Planning Releasing and Publishing Planned Deliveries and Shipments
SAP AG 2002
(C) SAP AG
SCM612
1
11.2 Vehicle Scheduling (VS): Unit Objectives
At the conclusion of thi s uni t, you will be able to: De scribe the TP/VS optimization process Identify the objectives of the optimization proce ss Create cost, alert, and optimization profiles Perform an interactive optimization run Release shipments Publish delivery and shipment data
SAP AG 2002
(C) SAP AG
SCM612
2
11.3 Vehicle Scheduling (VS): Business Scenario
The PC electronics manufacturer use s TP/VS to plan inbound and outbound shipments. Before planning can begin, the cost and optimization profiles must be created. To monitor various exception situations that can occur during the planning and tendering process, create an Alert Profile to report these exceptions.
SAP AG 2002
(C) SAP AG
SCM612
3
11.4 Vehicle Scheduling Process Flow (1) Configuration
Master Data
Modeling
Optimization (Load Consolidation & Vehicle Schedul ing)
Create/Transfer Shipments
Backorder Processing
Create/Transfer Deliveries
Carrier Selection
Carrier Tendering
Release Shipments
SAP AG 2002
After the basic TP/VS customizing, establishment of the appropriate master data and creation of the planning and cost profiles, the optimization of transportation demands is performed. This is called the optimization process. It may be performed interactively or in background. Backorder processing carried out in the global ATP component can affect the vehicle scheduling determination in TP/VS. Upon completion of the planning for one or more shipments, automatic carrier selection may be performed. Based on the carrier selection profile a carrier will be assigned to each shipment selected. In order to transfer planned shipments and their corresponding delivery documents to the OLTP or R/3 System for execution. The process of publishing must be performed first. An optional process that is part of the collaborative planning strategy of supply chain management is carrier tendering. The carrier tendering process, available in different scenarios, gives the shipper the ability to notify potential carriers of the availability of a shipment and its characteristics. The carrier, in turn, can accept or decline the tender offer and report that decision back to the shipper using various automated techniques. After shipments are published, they and their related delivery documents can be transferred to the OLTP or R/3 System for execution. This step represents the final process in the Vehicle Scheduling (VS) process flow.
(C) SAP AG
SCM612
4
11.5 Transactional Exchange relevant for Vehicle Scheduling
Transfer R/3Sales Order to APO via CIF
Create R/3 Sales Order
Create APO Order
OPTIMIZER Transfer Shipment to R/3via CIF
Release Shipment
Allocate Carrier
Allocate Vehicle Resource, Consolidate, Route Opt., Scheduling
CS-Optimizer
Adjust / Optimize Shipment
SAP AG 2002
Sales orders are created in the R/3 System and then transferred to APO via the CIF. The transactions required are CFM1 for creating an integration model and CFM2 for activating and deactivating the integration model. VS consists of a two-step optimization process: 1. Optimization on the basis of planning costs: Using an optimization and cost profile, the optimizer decides what has to be transported by which method/vehicle, when it needs to be transported, and over what transportation lane the shipment should be taken. 2. Carrier Selection: On the basis of a carrier selection profile, a carrier is assigned based on real freight costs, business share, and/or priority. After the optimization processes have been completed, the shipments and related delivery documents are published and transferred to the OLTP-R/3 System.
(C) SAP AG
SCM612
5
11.6 VS Optimizer: How does it work? The problem of the Traveling Salesman cons ists in the detection of the s hortest way (or one of the shortest ways), whic h connects a numbe r of locations a traveling salesman has to visit on a sales tour.
SAP AG 2002
The Travelling Salesman Problem (TSP) belongs to a group of problems that cannot be solved optimally in a reasonable time (NP-complete problems). The Vehicle Scheduling Problem in TP/VS is a generalization of the TSP and is harder to solve. The algorithm uses search strategies to try and find a good solution during the given runtime. Usually, the solution found is not necessarily optimal.
(C) SAP AG
SCM612
6
11.7 VS Optimizer Process
Costs Phase 2: Non-Improvement Moves First Solution
Phase 1: Greedy Search
Solution Runtime SAP AG 2002
Vehicle Scheduling Optimization: What does it do? The optimizer tries to assign freight units to vehicles and determine a goods delivery order for each vehicle, so that total transportation costs are minimized. It has to consider several constraints (vehicle capacity constraints, opening hours, and so on). It has to take penalty costs into account as part of the total transportation cost. What the optimizer does not do: • Transportation chains with more than two reloading points; parallel chains • Handle resource optimization • Variable breaks (Resources or Vehicles) • Determination of shortest paths • Vehicle space optimization The Optimizer works on the basis of a step-by-step-search technique: First solution Generator: Sorts/Inserts orders and deliveries according to vehicle constraints (resources) Local improvement: Modifies the current solution (move) and accepts the modified solution, if cost criteria is met. Phase 1: Greedy Search Only cost improving moves are accepted Phase 2: Non-Improvement-Moves Frequent moves are penalized; non-improving moves are accepted Best solution found during runtime is returned.
(C) SAP AG
SCM612
7
11.8 Results of an optimization run 3.00E+08
2.50E+08
2.00E+08
C O S T
1.50E+08
1.00E+08
5.00E+07
1:21:43
1:15:32
1:09:26
1:03:11
1:00:55
0:51:57
0:49:35
0:46:43
0:44:06
0:32:16
0:26:26
0:25:25
0:21:43
0:17:38
0:15:03
0:11:25
0:03:08
0:02:02
0:01:15
0:00:37
0:00:19
0:00:10
0:00:00
0.00E+00
Elapsed Run Time SAP AG 2002
Duration of an optimization run depends on the following factors: Number of sales orders and deliveries Number of resources (Vehicle Resources and Handling Resources) Constraints and costs: For an optimization run, different constraints are considered for planning. There is a difference between hard and soft constraints: During an optimization run hard constraints cannot be exceeded. An example of a hard constraint is the capacity of a vehicle resource. The Optimizer tries to observe soft constraints such as the requirement date of a sales order item. Violation of soft constraints is possible and takes into account the penalties (for example, early/late delivery). Schedules (train, ship, and so on) Number of depot locations (return trips for own vehicles) Vehicle/location (in-)compatibility Vehicle/Transportation Group (in-)compatibilities Transportation Group/Transportation Group (in-)compatibilities Maximum time a freight unit may be stored at a location (only relevant for cross-docking locations) Limits on distance, duration, and stopovers Opening hours
(C) SAP AG
SCM612
8
11.9 Constraints
Vehicle Capacity
Schedules of Vehicle Types (Trains, Ships, Aircraft, and Trucks)
Depot Location
Vehicle (In-) Compatibibility by Location
Vehicle Type/Transport Group (In-) Compatibility
Optimizer Constraints
Handling Resources
Opening Hours of Locations
Maximum Storage Time at Location Transport Group/Transport Group (In-) Compatibility
Lim its on Distance, Duration, Stopovers
SAP AG 2002
Vehicle capacities are defined in the vehicle tab in the Resource master data. Vehicle (in-)compatibilities for Locations are defined in Location master data in the TP/VS tab. The maximum time a freight unit may be stored at a location is defined in the Location master (TP/VS tab, Goods wait time). This constraint is used only in cross-docking scenarios. Load/Unload handling resources and opening hours are defined in the Resources tab of the Location master: • Specify the resource used to load and unload a vehicle during a delivery process. You must also define the resource consumption (in pieces), which are required for delivery (Docks, forklifts, and so on) Each freight unit uses the same capacity, independent of its size; the capacity is used during the load/unload time. • Opening hours are also defined in the Resources tab of the Location master. You have to indicate the resource for which the opening times of this location are maintained. The break times of the resource define when the location is not available. • You can either define load/unloading times or opening hours, but not both. Note: Picking lead time as well as transportation creation time which are defined in the TP/VS tab of the location master are not relevant for the TP/VS optimizer. picking lead time is the time required to make an order from the APO system available before the material availability date of the OLTP system, so that picking can take place in the OLTP system based on the corresponding deliveries. Transportation creation time is the time required for the transportation documents to be transferred from APO to the OLTP system, so that the appropriate shipment documents can be created before loading begins.
(C) SAP AG
SCM612
9
11.10 Costs in Optimization
C O S T P R O F I L E
GENERAL GENERAL
LOCATION LOCATION
SHIPMENT SHIPMENT
DIMENSION DIMENSION
TRANSPORTATION TRANSPORTATIONLANE LANE
SAP AG 2002
Costs are defined using a Cost Profile. Costs are not real costs, they are relative costs to be used by the optimizer.
(C) SAP AG
SCM612
10
11.11 Location-Related Costs
LOCATION LOCATION
Delay costs are the costs imposed as a penalty for delayed delivery. Nondelivery costs are the costs imposed a s a penalty for nondelivery.
SAP AG 2002
Penalty costs are not actually a currency amount, but rather a theoretical value that is used by the Optimizer to calculate the most favorable delivery date. The maintained delay costs refer to the units (time units) specified in the same row. This unit is specified in days. Calculation of the penalty costs in the objective function are re-calculated in seconds.
(C) SAP AG
SCM612
11
11.12 Penalty Costs: Delayed Delivery and Non-Delivery Costs
COST PROFIL E
CUSTOMER LOCATION MASTER SAP AG 2002
Delay and non-delivery costs can be defined location dependent. For each location, a certain priority can be defined, and for each priority different penalty costs can be specified. Note: The TP/VS optimizer does not use the delay/non-delivery costs which are defined in the Location Product master. Those costs are only used by SNP. Note: The penalty costs are maintained on a daily basis. Calculation of the penalty costs in the objective function are recalculated in seconds. The priority in the General tab of the location master data corresponds to the priority on the Location tab in Cost profile. Orders for locations with a certain priority receive the appropriate penalty costs for non-delivery or delayed delivery. This priority is taken into account if you maintain a delivery priority in your order. Enter the value one for the highest priority. The higher the number entered, the lower the priority. If you do not enter a value, the system automatically assigns the value zero, giving the location the highest priority.
(C) SAP AG
SCM612
12
11.13 Shipment-Related Costs
SHIPMENT SHIPMENT
Fixed transportation costs are the one-off costs incurred by using the vehicle(s) in question – irre spective of the actual transportation criteria (carrier, distance, and so on).
SAP AG 2002
(C) SAP AG
SCM612
13
11.14 Dimension-Related Costs
DIMENSION DIMENSION
Here you maintain the variable costs of a shipment
SAP AG 2002
Cost dimension is the dimension on which the transportation costs and cost unit are based. You also have to maintain the Cost Unit. Quantity – costs per unit and distance Distance – costs per distance unit (e.g. km) Duration – costs per time unit (e.g. day) Stopovers – costs per additional stop Definition of maximum distance/duration/number of stopovers Example 1: Variable transportation costs – Distance related Cost dimension Transportation cost Cost unit distance 50.00 KM => costs of 50.00 per KM Note: The dimension quantity is related to the transported quantity per KM Example 2: Variable transportation costs – Weight and distance related: Cost dimension transportation costs Cost unit quantity 2.00 KG => transportation costs of 2.00 per KG per KM. If the transportation route has a distance of 100 km, then the costs for 30 KG are calculated as 2.00 x 30 KG x 100 KM = 6,000. For 200 km, we would have costs of 12,000. Instead of the variable costs defined in the Dimensions tab of the Cost profile, you may also use the costs from the tab Transportation Lane.
(C) SAP AG
SCM612
14
11.15 Stopovers, used in Cost Profile
Lane 1
Loc. A
Lane 2
Loc. B Stopover 1
Lane 3
Loc. C Stopover 2
Loc. D
+1
SAP AG 2002
Number of stopovers: Depot → Customer A → Customer B → Customer C => 2 stopovers (source and target location in a route are not taken into account for calculating the number of stopovers). You have to maintain the number of stopovers + 1 (you have to maintain the number of lanes).
(C) SAP AG
SCM612
15
11.16 Costs for Transportation Lane
TRANSPORTATION TRANSPORTATIONLANE LANE
If you want to plan on basi s of costs maintained for special lanes, define on the dimension tab that costs from the transportation lane tab should be chosen.
SAP AG 2002
You have to maintain transportation costs for the unit of measure on which the specified product transportation costs are based (means what unit of measure you have maintained on the dimension tab).
(C) SAP AG
SCM612
16
11.17 Vehicle Scheduling Alert Profile
SAP AG 2002
Vehicle Scheduling Alert Profile is created in the Alert Monitor. The following are alert types that can be selected for inclusion in a VS Alert Profile: Alerts that are generated during the optimization run: - Check availability; Order due date changed by VS - Order not planned in Transportation Planning - Handling or transportation resource overload - No shipment generated by optimizer Alerts that can be generated during carrier selection or tendering: No carrier found Proposed delivery date changed by external carrier - Proposed shipment declined by external carrier - Proposed delivery date already in execution changed by external carrier - Proposed shipment already in execution declined by external carrier The Alert Profile is entered in the Optimization Profile.
(C) SAP AG
SCM612
17
11.18 Optimization Profile (1) Planning Data
Planning Version and Model
Depot Selection
Transfer Requirements (Sales orders, Deliveries, Stock Transport Orders and so on)
Planning Horizon
Offset Offset End
SAP AG 2002
There are three tabs to maintain settings for the optimization profile: Planning Data General Settings Automatic Shipment Creation In the Planning tab, the parameters include: • Version: the planning version to be used during Interactive Planning. • Depot Selection/With No Depot Locations Refers to resources that have not been assigned to a depot location. Resources can be assigned to specific locations. Choose With no depot locations when you want to select all resources that are not assigned to a depot location. A depot location can be a production plant, distribution center, supplier, carrier, or MRP area. Transfer Requirements define the demand horizon, the demand categories, source, and target locations. The Planning Horizon defines the period within which shipments should be planned.
(C) SAP AG
SCM612
18
11.19 Planning Horizon
Start of Planning Horizon
today
10 Days
Latest Requested Delivery Date
50 Days
Offset
End of Planning Horizon
9 Days
End of Offset Planning Horizon
= Sales Order = Material Availability Date = Requested Delivery Date SAP AG 2002
Offset in days: Starting from current date, defines the period (in days) after which the planning horizon should commence. The planning horizon commences after this period has elapsed. You can also maintain the offset duration to the exact hour and minute. This can result in either of the following: Time-dependent: If offset (in days) is set to zero, the planning horizon commences from the current time, after the offset duration has elapsed (in hours and minutes). Time-independent: If offset is set to one or higher, the planning horizon commences after the offset in days plus the maintained offset (in hours and minutes) from 0:00h. If you want to specify the offset more precisely, specify it in hours and minutes via Offset Duration. Example: Time dependent: Offset in Days=zero Offset Dur=3:00 means after three hours from current time Time independent: Offset in Days=one Offset Dur=7:00 means after one day and seven hours, (the seven hours are counted after the end of the first day, from 0:00 am the next day) Note: A day is defined as being 0:00h until 23:59h and the time refers to the local time zone of user End of Offset Indicates a time span in days. For example, if you enter three, there is a period of three days after the latest required delivery date during which the order can be executed. If you enter a zero, the order must be executed on the latest delivery date.
(C) SAP AG
SCM612
19
11.20 Optimization Profile (2) Transfer Requirement
Demand Horizon
Demand Categor y
Source Locations
Target Locations
SAP AG 2002
The Transfer requirements screen is accessed by selecting Multiple selection in the Transfer Requirements box on the Planning Data tab of the Optimization Profile screen. The tabs located in the Transfer Requirement screen are used to: • Define the time period that will be used to select the requirements (Sales Orders, Deliveries, Stock Transport Orders, and so on) • Select the documents to be planned (the requirements). • Select the Source Locations to limit the selection of the outbound requirements. • Select the Target Locations to limit the selection of the inbound requirements.
(C) SAP AG
SCM612
20
11.21 Demand Horizon
Start of Dem and Horizon
today
.
10 Days . Offset
.
End of Dem and Horizon
.
. 50 Days . . Dem and Horizon = Duration
= Sales Order = Material Availability Date = Requested Delivery Date
Sales Order is not included in defined Demand Horizon if the selection is made by Requested Delivery Date.
SAP AG 2002
The Demand Horizon defines which sales orders should be planned. The Offset in the Relative Horizon defines the period (in days, beginning at the current date) after which the demand horizon is to begin. This number can be either positive (if the offset time frame falls in the future) or negative (if the offset began in the past). The Offset is used when a concrete start and end date or start and end time for a horizon cannot be set. Example If an Offset of seven is defined, the selection of material availability/requested delivery dates for the orders begins eight days after today. The Duration in the Relative Horizon is used as follows: Start of demand horizon: Current date + Offset End of demand horizon: Current date + Offset + Duration. For example, all orders that have their material availability/requested delivery date within this horizon should be selected. The Selection MaAvailDat selection box controls if order selection is executed according to the material availability date (indicator set) or according to the requested delivery date (indicator not set).
(C) SAP AG
SCM612
21
11.22 Demand Categories
SAP AG 2002
The Demand category controls which requirements categories are included during Interactive Planning. The categories can be combined with each other (for example, a combined outbound/replenishment scenario). However, disconnected relationships do not work. For example, an inbound/outbound combination. Customerdesigned ATP categories can be used to enhance these categories. The following lists identify the various order categories by transportation requirement. Inbound: AH Purchase order memo BF Order item schedule line BV Line in a scheduling agreement Stock transports: (AH) Purchase order memo (only if necessary) BF Order item schedule line BI Stock transport order BR Delivery (EI) TLB: Purchase requisition (only if necessary) (IT) VMI delivery (only if necessary) Outbound: BM Sales order BQ Delivery free of charge BR Delivery BT Returns delivery • TLB: EI TLB: Purchase requisition EK TLB: VMI order EQ Replenishment delivery ER VMI delivery
(C) SAP AG
SCM612
22
11.23 Optimization Profile (3) General Settings
Cost Profile
Runtime for the Optimizer in seconds
Vehicle Scheduling Alert-Profile
SAP AG 2002
Assign your cost and alert profile to the optimization profile on this tab.
(C) SAP AG
SCM612
23
11.24 Optimization Profile (4) Automatic Shipment Generation (for Parcel or TLB orders)
Defines which deliveries are excluded from VS (for example, Parcel)
Deliveries up to the upper limit are transported with the specified resource
Deliveries over the lower limit are transported with another specified transportation mode (for example, FTL)
Category Selection
SAP AG 2002
(C) SAP AG
SCM612
24
11.25 Vehicle Scheduling Consistency Check
SAP AG 2002
After modeling your Supply Chain and finishing IMG-Activities, run the report /SAPAPO/VSCC. Use the transaction /SAPAPO/VSCC.
(C) SAP AG
SCM612
25
11.26 Interactive Planning (1)
Features Multi-Frame/Multi-View Design
Planned Shipments
Shipment A ssigned Orders Unassigned Orders for Consolidation Resource, Shipments, and Order Overview
SAP AG 2002
Transportation Planning/Vehicle Scheduling→ Planning → Interactive Vehicle Scheduling. The Vehicle Scheduling – Selection screen appears. Select an optimization profile. If a large number of resources or locations have been maintained, it may make sense to use resource selection. The selected settings are saved as variants. Choose Execute to get into the interactive vehicle scheduling planning. A selection area (shuffler) on the left side of the screen displays three different views (resources, shipments, and orders) in which a planning object can be selected Tabular planning on the right side of the screen covers the three different planning tables, or online scheduling, which contains information on all shipment activities in graphical form (a different display of tabular planning). Tabular planning consists of three tables: • Transport. activities All transportation activities (shipment assignments/itineraries) for the orders assigned to the planning object are displayed. The transportation number, the start, finish, and gross/net duration of the transportation activities are displayed. • Assigned/unplanned orders All of the (scheduled) orders assigned to the planning object in the planning horizon are displayed in the upper table. • All of the orders that are not scheduled or are to be scheduled are displayed in the lower table if they were selected according to the criteria defined in the optimization profile for order selection (selection horizon, source locations, and order categories) and are relevant for planning in the current planning run.
(C) SAP AG
SCM612
26
11.27 Interactive Planning (2) Re source view
All vehicle resources are displayed which:
Are not assigned to a depot location Are assigned to one of the selected depot locations Shipment view
All shipments that have at least one shipment activity completely or partially within the planning horizon are displayed
Is used to change, reschedule, or delete shipments that are already scheduled
Order view
All shipment-related data for individual orders are displayed
Is used to displa y the itinerary of the individual orders
SAP AG 2002
(C) SAP AG
SCM612
27
11.28 Create a shipment manually
1.
3.
2.
SAP AG 2002
You are in the maintenance view for interactive vehicle scheduling: Vehicle Scheduling – Resource. Double-click a resource in the left area of the screen. The screen name displays the resource description. In tabular planning, go to the right screen area when you can move orders from the planning table Not yet scheduled/to be scheduled to the planning table Assigned/unplanned shipments. Use Drag & Drop to do this, or choose Assign order. To remove an order from the table, choose Remove order. The Transportation Scheduling Specifications for Scheduling screen appears (see next page). Here you maintain: Loading and unloading durations Sequence of the stops Transportation duration Arrival or departure date and time The default values for the loading duration are determined in Transportation and Shipping Scheduling. A default value is also generated for the itinerary determined by the drive to all source locations and to all target locations. The sequence of the stops is determined by setting the stopoff sequence. The transport duration is read from the transportation relationships. They can be adjusted if necessary. At least one date must be entered for each shipment (usually the arrival time at the last target location). After you confirm, a shipment is created as long as there is a possible date for the execution of the shipment in the planning horizon, and the resource selected has enough capacity. Confirm your entries with Enter. In the Transportation activities planning table and the upper planning table of Assigned/unplanned shipment units, a line is added with the corresponding information.
(C) SAP AG
SCM612
28
11.29 Create Shipments Manually
SAP AG 2002
While you plan manually, the following restrictions apply: Vehicle resource capacities (as long as the resources are planned finitely) Resource time streams (including resource breaks, shifts, and unscheduled breaks) Loading and unloading resources at locations (including capacities and time streams) Opening times Trips to and from depot location (for own means of transport) Empty running distance Desired dates for arrival and departure Planning horizon
If the vehicle is assigned to a transportation vehicle that is not suitable for schedules and a shipment is created, this vehicle resource is not available for other shipments for the duration of the shipment, regardless of any remaining capacity.
(C) SAP AG
SCM612
29
11.30 VS Optimization Run Interactive Optimization
or Optimizing in the Background SAP AG 2002
Interactive Optimization From the interactive vehicle scheduling Vehicle Scheduling Resource screen, select VS Optimizer. Optimizing in the Background Transportation Planning/Vehicle Scheduling (TP/VS) → Planning → Planning in the Background → Schedule Optimization Run. Enter a job name. Choose an optimization profile. Choose Enter. The Start Times screen appears. Specify a date for background optimization. Choose Save. The screen closes and the message Background job was successfully scheduled appears in the message bar. The Optimization is carried out in the background at the time you selected. If the optimization run finishes without any problems or messages being displayed, the Optimizer does not create any transports. Reasons for this include: Non-delivery costs are so low, the Optimizer determines that non-delivery is cheaper than the transport of the order. Transportation lanes are missed. Total time of transport activities, including work breaks, is too long for the planning horizon.
(C) SAP AG
SCM612
30
11.31 Optimization Logfile
SAP AG 2002
(C) SAP AG
SCM612
31
11.32 History of Optimization Runs
SAP AG 2002
To get documentation of the Optimizer actions during an Optimization run, use Transaction /SAPAPO/OPT11. For analysis and error handling set the Dump Level to 1 in /SAPAPO/OPT10. In transaction /SAPAPO/OPT11 you can see if input and/or output data is written.
(C) SAP AG
SCM612
32
11.33 Changing Shipments
2. 1.
3.
SAP AG 2002
Reschedule on the Vehicle Scheduling – Shipments screen. Select a shipment (by double-clicking a shipment in the left screen area) and choose Reschedule shipment on the Transportation activities tab. If additional orders are added to a shipment in the transportation view, the whole shipment is rescheduled. You can do this until the shipment has been released.
(C) SAP AG
SCM612
33
11.34 Deleting Shipments
SAP AG 2002
Delete a shipment in the left screen area of the Vehicle Scheduling – Shipments screen by doubleclicking the shipment, clicking the right mouse button, and choosing Delete shipment. If you deallocate all of the orders assigned to a shipment, the shipment is also deleted. If an order is assigned to a shipment to be deleted as well as to other shipments, it is deallocated from all shipments. You can do this until the shipment has been released.
(C) SAP AG
SCM612
34
11.35 On-Line Scheduling View
Featuring Graphical Drop&Drag for Scheduling Transportation Activities and Resources
SAP AG 2002
Online scheduling: In the Transportation activities chart, the orders are displayed with their transportation activities on a time axis. This time axis corresponds to the planning horizon defined in the optimization profile. The activities load, transport, and unload are displayed in the form of bars, each in a different color. These bars cover the start and finish of activities. In the Resources chart, all of the resources involved in the shipments are displayed. This includes all of the vehicle resources, handling resources, and opening time resources. Resource breaks are displayed in gray.
(C) SAP AG
SCM612
35
11.36 Resource Utilization View
SAP AG 2002
You can maintain a planning table which shows your resources and their used capacities in the customizing of PP/DS. Choose: Advanced Planner and Optimizer (APO) → Supply Chain Planning → Production Planning and Detailed Scheduling (PP/DS) → Product Planning Table → Detailed Planning Board in the Product Planning Board → Maintain DS Planning Board Profiles.
(C) SAP AG
SCM612
36
11.37 Maintenance of Resource Utilization View
SAP AG 2002
The standard profile for TP/VS is SAP004. Never change this profile. Copy it to a user specific copy and enter your user name to the field Customizing ID. Mark your planning table profile and select Chart on the left side. You will see two charts: one Transportation activity and two Resources. To add a resource utilization view press New entries. In the upcoming screen enter a name on top; the chart number is three. Select in the next step the chart object one (Resource). In the field Displayed objects select Resource load, go to Histogram data (last tab at the bottom) and maintain the look of the diagram. Go to Interactive Planning Board (/SAPAPO/VS01) and select Overview Plan Board. There you will now also see the capacity of your resources. For a more detailed view you also can choose on the application side in Production Planning → Interactive Production Planning → Detailed Scheduling Planning Board → Variable. View the tab Planning Board. Put in your profile and choose Execute.
(C) SAP AG
SCM612
37
11.38 Exception Management
Features Interactive View of Alert Monitor
SAP AG 2002
View the alerts in the Alert Monitor window (Alert Monitor → Display alerts) Take action on alerts in the Alert Monitor window (access context menu with right mouse click). There are three possible priority levels: Error Warning Information Alert types are automatically assigned certain priority levels, but you can change the priority level of an alert in APO Customizing.
(C) SAP AG
SCM612
38
11.39 Set up Alerts for TP/VS
SAP AG 2002
Maintain an alert profile if you want to track Vehicle Scheduling alerts in APO. The profile allows you to maintain a user-specific selection of alerts corresponding to your area of responsibility. To set up Alerts for TP/VS choose APO Menu: Supply Chain Monitoring → Current Settings → Set Alert Monitor or choose transaction code /SAPAPO/AMON_SETTING. Determine planning version and time frame for alert selection in initial settings screen. If no version is defined, the system considers the version of the VS optimization profile Select Maintain profile, name your alert profile and choose the alerts you want to achieve. You also have to assign the relevant optimization profile. Save and go back. Assign your alert profile to the version-dependent alert selection. Save. Note: Keep alerts to a minimum. Too many alerts slow performance
(C) SAP AG
SCM612
39
11.40 Vehicle Scheduling Process Flow (4) Configuration
Master Data
Modeling
Optimization (Load Consolidation & Vehicle Schedul ing)
Create/Transfer Shipments
Backorder Processing
Publishing
Create/Transfer Deliveries
Carrier Selection
Release Shipments
Carrier Tendering
SAP AG 2002
(C) SAP AG
SCM612
40
11.41 Releasing Shipments
SAP AG 2002
Before each optimization run, all (fixed) shipments that are not yet released are deallocated. The optimizer reschedules the orders. For an order to be fixed, it must be released (published). When a shipment is released: Planning result is accepted as final Shipment is prepared for transfer to the OLTP system Published shipment is not deallocated before an optimization run Optimizer considers its resource load as a starting solution Process Flow: Vehicle Scheduling – Shipments view. To release orders, select one or more shipments in the left area of the screen by double-clicking them. Choose Release shipment. Note: After you release the shipments, you cannot make any changes to them in the APO System. There is one exception, if you use manual Carrier Selection, you are able to choose or change your carrier.
(C) SAP AG
SCM612
41
11.42 Communication Layer
Publishing (Live Cache)
Tendering on Planned Shipments
VS-Communication Layer
EDI XML WEB
Orders Orders
Deliveries Deliveries Shipments Shipments
SAP AG 2002
Executable function releasing planned shipments from APO into the Communication Layer
The VS-Communication Layer is a collection of database tables which store detailed order/delivery/shipment information.
Shipments are given a firm status and made available for tendering
(C) SAP AG
SCM612
42
11.43 Publishing Shipments
Data can be transferred interactively to
obtain an overview of the documents to be transferred
make changes to the due date horizon of the document transfer
earlier transfer of individual documents
SAP AG 2002
You have made the required settings in Customizing: Maintain the Basis Settings in the activities for Publication. Maintain the settings for Transportation Planning/Vehicle Scheduling (TP/VS) under Interfaces. In the APO menu, choose Transportation Planning/Vehicle Scheduling → Environment → OLTP Interface and then choose, one after the other, the following activities: Transfer Orders to Delivery Generation Check Release of Planned Shipments Transmit Planned Shipments to OLTP System Transfer Orders to Delivery Generation The Selection of orders to be transferred dialog box appears in which you specify the due date horizon for which you want to display planned orders. A list of the predecessor documents then appears (orders, purchase requisitions, and so on). You can confirm them or postpone transferring them. Choose Execute. The Display logs screen appears containing information on the current user of the log and an list of the orders that are currently being transferred. Check Release of Planned Shipments An overview of the released planned shipments appears. This step is important to make sure that all predecessor documents (for example, sales orders) have been converted to deliveries, since this is a prerequisite for creating a shipment. Transmit Planned Shipments to OLTP System The Selection of shipments to be transferred dialog box appears in which you specify the due date horizon for which you want to display planned shipments. A list of these shipments then appears. You can confirm them or choose them for earlier transfer.
(C) SAP AG
SCM612
43
Choose Execute. The Display logs screen appears containing information on the current user of the log and an list of the shipments that are currently being transferred.
(C) SAP AG
SCM612
44
11.44 Shipment Program (Outbound Process)
R/3 Plug-In (CIF)
APO Middleware (CIF)
Orders Sales Orders, Deliveries, and so on
Orders
-
Subscribe Key Selection Det. Dest. Sys Mapping Call BAPI
Optimization Load Consolidation Vehicle Scheduling
Creates
Outbound Shipment
Planned Shipments
SAP AG 2002
There is an executable for Releasing/Creating Shipments in the Execution System Uses APO Middleware to transfer or execute a create via CIF in real-time mode. For sales orders that are planned, the planned deliveries and shipments are reflected in the document flow of the orders.
(C) SAP AG
SCM612
45
11.45 Shipment Change Process
R/3 Plug-In (CIF) manual changes
APO Middleware (CIF) update
Orders
Orders
update manual changesShipments
update
Shipments
SAP AG 2002
Any planning-relevant change to an order will invalidate the shipment in APO. If the shipment consists of only the order that is changed, it will be deleted. If other orders exist in the shipment, the status of the shipment will be changed. Orders, deliveries and shipments must be changed in the OLTP System (R/3 System). Planning relevant changes will be updated in the APO system.
(C) SAP AG
SCM612
46
11.46 End Shipments
SAP AG 2002
By setting the flag Shipment end in OLTP R/3 System, the shipment in APO is no longer relevant for planning. A deletion indicator for those shipments is set. If a shipment has been deleted in the OLTP System, the shipment in APO will also be deleted. Those shipments and their deliveries for which a deletion indicator has also been set are deleted. To delete those shipments choose in APO Menu Transportation Planning/Vehicle Scheduling → Planning → Delete Shipments. The Display logs screen appears. Along with the general information on the user of this activity, a list of shipments that are due appears. Data on this screen can only be displayed. Choose Back to exit this screen. a deletion indicator is set for the delivery if you post goods issue or goods receipt. To delete those deliveries choose in APO Menu Transportation Planning/Vehicle Scheduling → Planning → Delete Deliveries. The Display logs screen appears. A deletion indicator is also set for a delivery, if: The delivery has been deleted in the OLTP System The delivery has been posted as a goods issue in the OLTP System and is not assigned to a shipment anymore The shipment has been deleted in the OLTP System To delete the delivery, choose in the APO menu: Transportation Planning/Vehicle Scheduling → Planning → Delete Deliveries. The Display logs screen appears. Along with the general information on the user of this activity, a list of deliveries that are due appears. Data on this screen can only be displayed. Choose Back to exit this screen.
(C) SAP AG
SCM612
47
11.47 Archiving Deliveries
To maintain the Archiving Settings choose in R/3 Customizing: Logistics Execution → Archiving
SAP AG 2002
From time to time, inbound and outbound deliveries that are no longer required in the system can be archived. To execute this function, use the archiving object RV_LIKP. This writes the deliveries to an archive file and then deletes them from the database. Central archiving is set up, executed, and managed using transaction SARA. During the archiving run, the deliveries are checked on the basis of different criteria as to whether they can actually be archived. These checks include (excerpt): Total status of the delivery is complete Delivery has reached the residence time (residence time in the system) The shipment to which the delivery belongs is complete You can determine the residence time yourself on the basis of the sales organization and the delivery type. As a rule, all the other checks cannot be changed.
(C) SAP AG
SCM612
48
11.48 Archiving Shipments
To maintain the Archiving Settings choose in R/3 Customizing: Logistics Execution → Archiving
SAP AG 2002
The archiving program checks several criteria for each shipment. A shipment can be archived if the following conditions are met: The creation date of the shipment must be at least N days in the past. The last change date fo the shipment must be at least M days in the past. The overall status of the shipment must be at least X. You set X in archiving control for transportation (column: Minimum overall status). All deliveries in the shipment must have transportation planning status C (fully planned). All deliveries in the shipment must have goods movement status ' ' (not relevant) or C (fully processed ). The shipment must have the overall shipment costs calculation status ' ' (not relevant) or C (completely processed). If the overall shipment costs calculation status of the shipment is C (completely processed), the relevant shipment cost document must already have been archived. This means that is must no longer exist in the system. During archiving, the document flow must be processed starting with the last document in the list. All shipments that are included in a transportation chain with the shipment currently being processed must also be fully relevant for archiving. This means, these shipments must also meet preconditions 1-5 and fall within the shipment number range you specified when you started archiving. The last five criteria are always checked in the program and cannot be altered. The first three criteria, however, can be set in Customizing (archiving control for transportation).
(C) SAP AG
SCM612
49
11.49 Available Functions for Mass Processing
Mass Processing Capab ilities
Optimization
Create Job Job Profile
Carri er Selection Create/Delete Deliveries Create/Delete Shipments
Schedule Job
Date Sequence: Job, Event, or operation
11 10
12
1 2
9
3 8
4 7
6 5
SAP AG 2002
The above sequence depicts the steps you perform to carry out mass processing. You can carry out several planning actions within one job as long as they have the same activity. For example, you might run a mass processing job that executes several macros at the same time, or a job that carries out a VS optimization, carrier selection then publishing of the data to the R/3 (OLTP) System. The sequence in which actions within one activity are processed depends on the sequential numbers you define for them in the activity. The system performs all actions for the first characteristic value before processing the second characteristic value. Consequently, if you want the system to perform one action for all characteristic values before it starts the next action, you must define separate planning activities. For each job, define the selection of data which should be considered in the processing of the job as well as the level to which it should be aggregated before the actions are executed. Planning jobs are reusable. See: APO SAP Menu → Transportation Planning/Vehicle Scheduling → Environment → OLTP Interface → Mass Processing Interface.
(C) SAP AG
SCM612
50
11.50 Mass Processing Job Log
Job Log Available
Date/Time of job
Status: red, yellow, green
Characteristic combinations processed
SAP AG 2002
The system can nowcreate a log of a mass processing job. Set an indicator on the job creation screen. The job log shows: Name of the job Date and time which the job started Whether the job completed successfully (green), with warnings (yellow) or with errors (red) A message relating to every characteristic value combination that was processed in the job along with long text You can also use the following functions: Show/hide all characteristic value combinations that completed successfully/with warnings/with errors Sort and filter according to characteristic value combination or message text Print, download, or send the current view of the log Define display variants for the log
(C) SAP AG
SCM612
51
11.51 Vehicle Scheduling (VS): Interactive Planning: Unit Summary
You are now able to: De scribe the TP/VS optimization process Identify the objectives of the optimization proce ss Create cost, alert, and optimization profiles Perform an interactive optimization run Release shipments Publish delivery and shipment data
SAP AG 2002
(C) SAP AG
SCM612
52
11.52Vehicle Scheduling (VS) Exercises Unit: Vehicle Scheduling (VS) Topic: Interactive Planning At the conclusion of this exercise, you will be able to: •
Create a Cost Profile to be used in VS Optimization
•
Create a TP/VS Alert Profile to monitor exception events in planning
•
Create an Optimization Profile for use with the VS Optimizer
•
Perform an interactive planning run and evaluate the results
•
Release shipments
•
Publish delivery and shipment data to the R/3 System.
As a member of the TP/VS implementation team, you are responsible for setting up the required profiles necessary to begin planning of transportation shipments using TP/VS. You are required to establish cost profiles that the optimizer will use in evaluating cost constraints related to various methods of transportation. To monitor the process for various exception situations, you will also create a VS Alert Profile that will be assigned to your optimization profile. As the last step before the interactive planning can begin, you must create the Optimization Profiles, that, will select the documents for planning. After the planning process has been completed, you will transfer the delivery and shipment data to the R/3 System using the publishing process.
1-1
For Model 000 create cost profiles for: general costs, location costs, shipment costs, and dimension costs as follows: Model:
000
General Costs: New Profile Name:
GRP##
Earliness Cost:
250.00
Location: Priority:
1
Delay Cost:
2000.000
Non-Delivery Cost: (C) SAP AG
1,000,000.000 SCM612
53
Priority:
2
Delay Cost:
1000.000
Non-Delivery Cost:
500,000.000
Shipment: Transport.Method:
FTL##
Fixed Trans. Cost:
50.000
Transport.Method:
LTL##
Fixed Trans. Cost:
40.000
Dimension: Transport.Method:
FTL##
Cost Dimension:
E – Distance
Transp.Costs:
1.00
Cost Unit:
KM
Transportation Max.: leave blank Cost Basis:
0 – Dimension
Transport.Method:
LTL##
Cost Dimension:
E – Distance
Transp.Costs:
.50
Cost Unit:
KM
Transportation Max.: leave blank Cost Basis:
0 – Dimension
Choose Save.
(C) SAP AG
SCM612
54
1-2
Create an Alert Profile in the Alert Monitor: VehSched alert profile: Description:
VSAP-##
VS Alert Profile Gr. ##
Check the following alerts: •
Check Availability. Order due date changed by Vehicle Scheduling
•
Order not planned in Transportation Planning
•
No Carrier Found
•
Handling or transportation resource overloaded
•
Optimizer: No transport created Choose Save.
1-3
Create an optimization profile for inbound shipments: Optimization Profile: OPIN-## Description: Inbound Shipments Gr. 18 Planning Data tab: Planning Version:
000 With no depot locations
Transfer Requirement: Fixed Horizon: Start date: Start time: End date: End time:
leave blank 00:00:00 leave blank 23:59:00
Demand Categories: AH, BF,BI, BR, BV Target Locations: 10##, 22## Choose Back. General Technical Settings: Cost Profile: GRP## Runtime Optimization: 60 Vehicle Scheduling alert profile: VSAP-## Autom. Shipment Generation:None Choose Save. 1-4
Run the Consistency Check on your inbound profile. If there are any errors you should correct the errors before proceeding. Transaction: /n/SAPAPO/VSCC
1-5
Create an Optimization Profile for outbound shipments: Optimization Profile: OPOUT-## Description: Outbound Shipments Gr. 18
(C) SAP AG
SCM612
55
Planning Data tab: Planning Version:
000 With no depot locations
Transfer Requirement: Fixed Horizon: Start date: Start time: End date: End time:
leave blank 00:00:00 leave blank 23:59:00
Demand Categories: BM,BQ,BR,BX,EQ Source Locations: 10##, 12##, 22##, 25## Choose Back. General Technical Settings: Cost Profile:
GRP##
Runtime Optimization:
60
Vehicle Scheduling alert profile: VSAP-## Autom. Shipment Generation:No Settings Required Choose Save. 1-6
Run the Consistency Check on your outbound profile. If there are any errors you should correct the errors before proceeding. Transaction: /n/SAPAPO/VSCC
(C) SAP AG
SCM612
56
1-7
Create an optimization variant and conduct an interactive vehicle scheduling run for inbound shipments: 1-7-1 Create a variant for the Vehicle Scheduling Selection screen after you have entered your optimization profile. Enter the following: Optimization profile: OPIN-## Select Enter. Selection period: Enter Start date: Today's Date End date: Today's Date + 4 Wks Resource: Use Multiple Selection to enter your resources, G##-FTRK01 – G##-FTRK05 G##-LTRK01 – G##-LTRK05 Choose Save to create the variant. Enter the Variant Name: OPIN-## Enter the Variant description: OPIN-##. Choose Save. 1-7-2 Initiate the optimization process and review the data that is displayed on the Vehicle Scheduling screen and review the unassigned Freight units. Answer the following questions: How many unassigned Freight units are there? ______ How many resources are available? _______ How many assigned/Unplanned Freight units? ______ How many shipments were created ? _______ Run the VS OPtimizer. Answer the following questions: How many unassigned Freight units are there? ______ How many resources are available? _______ How many assigned/unplanned Freight units? ______ How many shipments were created ? _______ Check the Alert Monitor: How many alerts were displayed ? ________ Save the session.
1-8
Create an optimization variant and conduct an interactive vehicle scheduling run for outbound shipments: 1-8-1 Create a variant for the Vehicle Scheduling Selection screen after you have entered your optimization profile. Enter the following: Optimization profile: OPOUT-##
(C) SAP AG
SCM612
57
Select Enter. Selection period: Enter Start date: Today's Date End date: Today's Date + 4 Wks Resource: Use Multiple Selection to enter your resources, G##-FTRK01 – G##-FTRK05 G##-LTRK01 – G##-LTRK05 Choose Save to create the variant. Enter the Variant Name: OPOUT-## Enter the Variant description: OPOUT-##. Choose Save. 1-8-2 Initiate the optimization process and review the data that is displayed on the Vehicle Scheduling screen and review the unassigned Freight units. Answer the following questions: How many unassigned Freight units are there? ______ How many resources are available? _______ How many assigned/unplanned Freight units? ______ How many shipments were created ? _______ 1-8-3 Create a planned and release a shipment manually from the sales order with only one line item. Use an LTL resource. 1-8-4 Run the VS Optimizer. Answer the following questions: How many unassigned Freight units are there? ______ How many resources are available? _______ How many assigned/Unplanned Freight units? ______ How many shipments were created ? _______ Check the Alert Monitor: How many alerts were displayed ? _______ Save the session. 1-8-5 Release the planned shipments. Shipment document number: _______________________ Shipment document number: _______________________ Shipment document number: _______________________ 1-8-6 Perform Manual Carrier Assignment for the shipments. Assign carrier 0000001058 to each shipment. 1-8-7 Choose Save. 1-8-8 Transfer the delivery data to the R/3 System using the publishing process. 1-8-9 Check the release status of all shipment documents. 1-8-10 Transfer the shipment data for your shipments to the R/3 System. (C) SAP AG
SCM612
58
1-8-11 View the delivery and shipment documents in the R/3 System for one of the sales orders.
(C) SAP AG
SCM612
59
Exercises Unit: Vehicle Scheduling (VS) Topic: Using Transportation Zone Hierarchies At the conclusion of this exercise, you will be able to: •
Understand the customizing settings and master data requirements necessary to use transportation zone hierarchies in shipment planning.
Due to the large customer base in your PC electronics company, you must reduce the number of transportation lanes required to plan shipments. To accomplish this and to provide a more accurate cost optimization, you will use the transportation zone hierarchy function. 2.1
(C) SAP AG
Although a transportation zone hierarchy has already been established, TZONE, you will review the pertinent customizing settings: 2.1.1
First, look at the hierarchy structure definition table. In this table the TZONE hierarchy is defined as a Location hierarchy with two levels (two is the standard and cannot be exceeded.).
2.1.2
The second customizing table is definition of the hierarchy itself and the link to the structure defined in the first table. There are some text fields defined here as well.
2.1.3
The third relevant table is the Maintain Transportation-Relevant Hierarchy table. In this table, you assign your transportation zone hierarchy to the VS application.
2.1.4
The transportation zone hierarchy should be created before any customer location data is transferred to APO. When the hierarchy is created first, the system will automatically update the hierarchy with the transportation zones and associated customer locations. To see your customers in the transportation zone hierarchy go to the Hierarchy master data table, verify that your customers are in transportation zones DE-D000060000, DE-D000070000 or DE-D000080000.
SCM612
60
2-1-5 To test the use of Transportation Zone Hierarchies: Create four sales orders: Sales Document Type: OR Sold-to:
T-S11A##
P.O.Number:
12-1-##
Requested Del. Date: Today + 3 weeks Material and Qty:
T-ATD2-## 50 PC
Document Number:
_______________________
Sold-to:
T-S22A##
P.O.Number:
12-2-##
Requested Del. Date: Today + 3 weeks Material and Qty:
T-ATD2-##
T-ATD3-## Document Number:
50 PC
50 PC
_______________________
Sold-to:
T-S33A##
P.O.Number:
12-3-##
Requested Del. Date: Today + 3 weeks + 1 day Material and Qty:
T-ATD2-##
T-ATD3-## Document Number:
50 PC
50 PC
_______________________
Sold-to:
T-S33A##
P.O.Number:
12-4-##
Requested Del. Date: Today + 3 weeks Material and Qty:
T-ATD2-##
T-ATD3-## Document Number:
(C) SAP AG
50 PC
50 PC
_______________________
SCM612
61
Use your optimizing profile OPOUT-## to plan the shipments and save the planned data but document the following: How many shipments were created? What were the optimized costs?
____________________ ____________________
2-1-6 To use the transportation zone hierarchy in planning, a transportation lane must exist between the source plants/DCs and the transportation zones. In addition, a circular transportation lane must exist in which the source and target locations are the transportation zone. In this exercise, you will check transportation zone DE-D000060000 for the circular relationship and add your Transportation Methods to the lane (FTL## and LTL##). 2-1-7 Check that a lane exists between your plant 12## and transportation zone DE-D000060000. If not, create it. 2-18-8 Go back to Interactive planning and re-run the VS OPtimizer and document the following: How many shipments were created? _____________________ What was the total optimized costs? _____________________ 2-1-9 Save your data.
(C) SAP AG
SCM612
62
11.53Solutions Unit: Vehicle Scheduling (VS) Topic: Interactive Planning 1-1
For Model 000, create cost profiles for: general costs, location costs, shipment costs and dimension costs as follows: APO SAP Menu → Master Data → Master Data for Transportation Planning/Vehicle Scheduling → /SAPAPO/CTRP - Maintain Vehicle Scheduling Costs Model name: 000 Select Change. General costs tab: Select Add rows. Add a row: Cost profile: GR## Earliness cost:250.000 Select the Location costs tab: Select Add rows. Add two rows: Cost profile: GR## Priority: 1 Delay costs: 2000.000 Nondelivery costs:1,000,000.000 Cost profile: GR## Priority: 2 Delay costs: 1000.000 Nondelivery costs:500,000.000
(C) SAP AG
SCM612
63
Select the Shipment tab: Select Add rows. Add two rows: Cost profile: GR## TransportMethod: FTL18 Fixed transp.costs: 50.000 Cost profile: GR## TransportMethod: LTL18 Fixed transp. costs: 40.000 Select the Dimension tab: Select Add rows: Cost profile: GR## TransportMethod: FTL18 Cost dimension: E – Distance Transportation costs: 1.000 Cost unit: KM Transportation Max: Leave blank Cost basis: 0 - Dimension Cost profile: GR## TransportMethod: LTL18 Cost dimension: E – Distance Transportation costs: 1.000 Cost unit: KM Transportation Max: Leave blank Cost basis: 0 – Dimension Choose Save. 1-2
Create an Alert Profile: APO SAP Menu → Supply Chain Monitoring → /SAPAPO/AMON1 - Alert Monitor → Choose Maintain profile. Under the Appl column on the left side of the screen, select the VS. VehSched alert profile: Description:
VSAP-##
VS Alert Profile Gr ##
Select the "check boxes" for the following alerts: •
Check Availability. Order due date changed by Vehicle Scheduling
•
Order not planned in Transportation Planning
•
No Carrier Found
•
Handling or transportation resource overloaded
•
Optimizer: No transport created Choose Save.
(C) SAP AG
SCM612
64
1-2
Create an Optimization Profile for inbound shipments: SAP Menu → Transportation Planning/Vehicle Scheduling → Environment → Current Settings → Transportation Optimization → S_AP9_75000203 - Define Optimization Profile Optimization Profile: OPIN-## Select Create. Description:
INBOUND SHPMNTS - GR ##
Under the Planning Data tab: Planning Version:
000
Select With no depot locations. In the Transfer requirements section: Select Multiple selections. In the Demand Horizon section: Select the Fixed Horizon. Enter End time:
23:59:00.
Leave the date fields blank. Select the Demand Categories tab. In the All remnts categ box, select the following: AH, BF, BI, BR, BV Select the single arrowhead pointing to the left. Select the Target loc. tab: In the All target locs section, select locations: 10##, 22## Select the single arrowhead pointing to the left. Choose Back. Select the General Techn. Settings tab: Enter: Cost profile: GRP## Runtime optimization: 60 Vehicle Scheduling alert profile: VSAP-## Choose Save. 1-4
Run the Consistency Check on your inbound profile. If there are any errors you should correct the errors before proceeding. Transaction: /n/SAPAPO/VSCC
1-5
(C) SAP AG
Model:
000
Profile:
OPIN-##
Create an Optimization Profile for outbound shipments:
SCM612
65
SAP Menu → Transportation Planning/Vehicle Scheduling → Environment → Current Settings → Transportation Optimization → S_AP9_75000203 - Define Optimization Profile Optimization Profile: OPOUT-## Select Create. Description:
OUTBOUND SHPMNTS - GR ##
Under the Planning Data tab: Planning Version:
000
Select With no depot locations. In the Transfer requirements section: Select Multiple selections. In the Demand Horizon section: Select Fixed Horizon. Enter End time:
23:59:00.
Leave the date fields blank. Select the Demand Categories tab. In the All remnts categ box, select the following: BM, BQ, BR, BX, EQ Select the single arrowhead pointing to the left. Select the Target loc. tab: In the All target locs section, select locations: 10##, 12##, 22##, 25## Select the single arrowhead pointing to the left. Choose Back. Select the General Techn. Settings tab: Enter: Cost profile: GRP## Runtime optimization: 60 Vehicle Scheduling alert profile: VSAP-## Choose Save. 1-6
Run the Consistency Check on your outbound profile. If there are any errors you should correct the errors before proceeding. Transaction: /n/SAPAPO/VSCC
1-7
Model:
000
Profile:
OPOUT-##
Create an optimization profile variant and conduct an interactive vehicle scheduling optimization run for inbound shipments: APO SAP Menu → Transportation Planning/Vehicle Scheduling → Planning → /SAPAPO/VS01 - Interactive Vehicle Scheduling
(C) SAP AG
SCM612
66
1.7.1
Create a variant for the selection screen of your optimization profile:
Enter the Optimization profile:
OPIN-##
Choose Enter. Planning Version:
000
Selection period: Enter Start date: Today's date Enter End date:
Today's date + 8 weeks
Planning area: Select the Multiple selection icon. Select the Ranges tab. Enter on one line: 1st col.: 2nd col:
G##-FTRK01 G##-FTRK05
Enter on next line:1st col.: 2nd col:
G##-LTRK01 G##-LTRK05
Select the Copy icon. Choose Save. In the ABAP:Save as variant screen: Enter OPIN-## as the Variant name. Enter OPIN-## as the Description. Choose Save.
(C) SAP AG
SCM612
67
1-7-2 Select the "Execute" button. On the Vechicle Scheduling screen you should see the purchase order that you created in the Transfer of Transaction Data unit listed at the bottom of the Tabular planning section. You should also see a list of your resources on the left side (the Shuffler area). Answer the questions in the Exercise. Select VS Optimizer. The TP/VS Optimizer screen will display. Select Execute. The Optimizer will run and you should see messages appear in the Optimizer box and you should get one shipment created. Select Confirm button (green check mark). Answer the questions in the Exercise. Select Alert monitor. Record any alert messages. Select Shipments in the Shuffler area. You should see your planned shipment. Double-click on it to bring the data into the Tabular planning area. Review the data on the lines that are displayed. Select the Overview Plng Board. Use Zoom to enlarge the viewing area. Right-click on the Date heading area. Select the Daily view. Scroll to the shipment data in the view. Notice the resource graphic corresponding to the shipment. Select the Obj. plng board. What is the difference between the two planning boards? _____________________________________________ _____________________________________________ _____________________________________________
(C) SAP AG
SCM612
68
Select the Details tab. Answer the following questions: What is the Source location? _______________________ What is the Target location? _______________________ Distance:
_______________________
Overall Status:
_______________________
Carrier Number:
_______________________
What is the resource assigned?
_______________________
Choose Save. 1-8
Create an optimization profile variant and conduct an interactive vehicle scheduling optimization run for outbound shipments: APO SAP Menu → Transportation Planning/Vehicle Scheduling → Planning → /SAPAPO/VS01 - Interactive Vehicle Scheduling 1-8-1 Create a variant for the selection screen of your optimization profile: Enter the Optimization profile:
OPOUT-##
Choose Enter. Planning Version: 000 Selection period: Enter Start date: Today's date Enter End date:
Today's date + 8 weeks
Planning area: Select Multiple selection. Select the Ranges tab. Enter on one line: 1st col.: 2nd col:
G##-FTRK01 G##-FTRK05
Enter on next line:1st col.: 2nd col:
G##-LTRK01 G##-LTRK05
Select the Copy icon. Choose Save. In the ABAP:Save as variant screen: Enter OPOUT-## as the Variant name. Enter OPOUT-## as the Description. Choose Save.
(C) SAP AG
SCM612
69
1-8-2 Select the Execute button. On the Vechicle Scheduling screen you should see the sales orders and stock transport that you created in the Transfer of Transaction Data unit listed at the bottom of the Tabular planning section. You should also see a list of your resources on the left side (the Shuffler area). Answer the questions in the Exercise. 1-8-3 To demostrate that a shipment can be created manually: Select one of the LTL resources listed in the Shuffler area by doubleclicking on it. The resource name should appear in the Title bar. Select the button to the left of the Sales order with the single line-item. Select Assign order in the toolbar of the unassigned area. The Transportation Scheduling Specifications for Scheduling box will be displayed next. You could enter scheduling date information here, if desired. Select the Choose icon (green check mark). A message box will be displayed. Choose Continue. The planned shipment will be created. Select Shipments in the Shuffler. Select the planned shipment you just created. Select Release shipment in the toolbar above the shipment line. 1-8-4 Select the VS Optimizer button. The TP/VS Optimizer screen will display. Select the Execute button. The Optimizer will run and you should see messages appear in the Optimizer box and you should get two shipments created. Select Confirm button (green check mark). Answer the questions in the Exercise. Select Alert monitor. Record any alert messages. Select Shipments in the Shuffler area. You should see your planned shipments. Double mouse-click on one of the shipments to bring it's data into the Tabular planning area. Review the data on the lines that are displayed. Select the Overview Plng Board. Use Zoom to enlarge the viewing area. Right-click on the Date heading area. Select the Daily view. Scroll to the shipment data in the view. (C) SAP AG
SCM612
70
Notice the resource graphic corresponding to the shipment. Select the Obj. plng board. What is the difference between the two planning boards? _____________________________________________ _____________________________________________ _____________________________________________ Select the Details tab. Answer the following questions: What is the Source location? _______________________ What is the Target location? _______________________ Distance:
_______________________
Overall Status:
_______________________
Carrier Number:
_______________________
What is the resource assigned?
_______________________
Choose Save. 1-8-5 Release the shipments: Select Shipment in the shuffler. Select all of the planned shipments in the list. The status of each shipment should be changed to Published. 1.8.5
Perform manual Carrier Selection.
Select all of the Published shipments. Select Carrier Selection. In the Carrier profile dialog box: Select Carrier number. Enter 0000001058 in the Carrier Number field. Select Execute. You should get amessage that carrier selection was performed successfully. Select the Details tab. What is the Overall status? ___________________________________________________ What is the Carrier number? ___________________________ 1-8-7 Choose Save. 1-8-8 Perform the "publishing" process by first transferring the delivery data: APO SAP Menu → Transportation Planning/Vehicle Scheduling → Environment → /SAPAPO/VS50 - Transfer Orders to Delivery Generation In the Selection box, enter a selection date that is Today's date + 6 weeks. Select the Execute button. (C) SAP AG
SCM612
71
In the list of orders displayed, SELECT ONLY YOUR ORDERS. Select Publish orders. Check the Log. Your orders should have been transferred. Choose Back. 1-8-9 Perform the Check Release of Planned Shipments process: APO SAP Menu → Transportation Planning/Vehicle Scheduling → Environment → /SAPAPO/VS52 - Check Release of Planned Shipments The Display Log should have your shipments listed. Choose Back. 1-8-10 Perform the transfer of shipment data to the R/3 System: APO SAP Menu → Transportation Planning/Vehicle Scheduling → Environment → /SAPAPO/VS51 - Transmit Planned Shipments to OLTP System In the Selection of shipments for transfer box, enter a date that is today's date + 6 weeks. Select Execute. SELECT ONLY YOUR SHIPMENTS FOR TRANSFER!!! Select the Publish orders button. The Display log should list your shipments as being transferred,
(C) SAP AG
SCM612
72
1-8-11 Display the R/3 delivery and shipment data that was generated during the publishing process: R/3 SAP Menu → Logistics → Sales and Distribution → Sales → Order → VA02 – Change In the Search criteria field: Sold-to party enter: T-S11A## Select the Search button. Select your order. Choose Enter. From the Sales Order Overview screen, place the cursor in the Sold-to party field. Choose: Environment → Display document Flow In document flow, select the shipment document. Go to the Shipment document overview screen and: Verify the carrier assignment: Verify the Stages:
______________
______________
What is the Shipment Type?: ______________ What is the Trans.Pl.Point?: ______________
(C) SAP AG
SCM612
73
Solutions Unit: Vehicle Scheduling (VS) Topic: Using Transportation Zone Hierarchies 2-1
To establish a transportation zone hierarchy, there are three relevant customizing tables: 2-1-1 Define Hierarchy Structure at: APO IMG → Advanced Planner and Optimizer (APO) → Master Data → Hierarchy → Define Hierarchy Structure 2-1-2 Define the Hierarchy at: APO IMG → Advanced Planner and Optimizer (APO) → Master Data → Hierarchy → Define Hierarchy 2-1-3 Maintain Transportation-Relevant Hierarchy at: APO IMG → Advanced Planner and Optimizer (APO) → Transportation Planning/Vehicle Scheduling (TP/VS) → Basic Settings → Maintain Transportation-Relevant Hierarchy 2-1-4 Display the Transportation Hierarchy Zone master data table: APO SAP menu → Master Data → /SAPAPO/SCCRELHSHOW – Hierarchy Hierarchy:
TZONE
Select the Display Hierarchy objects button. Drill down in zones: DE-D000060000 DE-D000070000 DE-D000080000 Verify that your customers are in these zones. 2-1-5 Create four sales orders: R/3 SAP Menu → Logistics → Sales and Distribution → Sales → Order → VA01- Create Enter and save the sales orders. Record the document numbers.
(C) SAP AG
SCM612
74
2-1-6 Run Interactive Planning: APO SAP Menu → Transportation Planning/Vehicle Scheduling → Planning → /SAPAPO/VS01 - Interactive Vehicle Scheduling Use your variant OPOUT-18. When running the VS Optimizer, record your number of shipments planned and the total optimized costs. 2-1-7 Display the transportation lanes: APO SAP Menu → Master Data → /SAPAPO/SCC_TL1 - Transportation Lanes Display transportation Lane: Source:
12##
Target:
DE-D00006000
Change transportation Lane: Source:
DE-D000060000
Target: DE-D000060000 Update the lane with your Transportation Methods: FTL## LTL## 2-1-8 Run Interactive Planning: APO SAP Menu → Transportation Planning/Vehicle Scheduling → Planning → /SAPAPO/VS01 - Interactive Vehicle Scheduling Use your variant OPOUT-18. When running the VS Optimizer, record your number of shipments planned and the total optimized costs. 2-1-9 Choose Save.
(C) SAP AG
SCM612
75
12 Carrier Selection
Contents: The Carrier Selection process Customizing activities related to Carrier Selection
SAP AG 2002
(C) SAP AG
SCM612
1
12.2 Carrier Selection: Unit Objectives
At the conclusion of thi s uni t, you will be able to: Make the required customizing settings related to carrier selection Perform carrier selection for planned shipments
SAP AG 2002
(C) SAP AG
SCM612
2
12.3 Carrier Selection: Business Scenario
After completing the shipment planning process, the PC manufacturer wants to use the TP/VS carrier selection proce ss to automatically assign freight carriers to the planned shipments.
SAP AG 2002
(C) SAP AG
SCM612
3
12.4 Vehicle Scheduling Process Flow (3) Configuration
Master Data
Modeling
Optimization (Load Consolidation & Vehicle Schedul ing)
Create/Transfer Shipments
Backorder Processing
Create/Transfer Deliveries
Carrier Selection
Carrier Tendering
Releasing Shipments
SAP AG 2002
The Carrier responsible for transporting the shipment is selected after the shipment and its deliveries are determined in Optimization and Scheduling. Carrier selection is performed through specific rules in APO or through private/public exchanges in the R/3 System. Rules-based carrier selection is based on the lowest total cost, highest priority, or pre-defined business share amongst the eligible carriers. These rules are stored in the Carrier Optimization Profile. Carrier selection does not need to be performed in APO, but can be manually completed in the R/3 system.
(C) SAP AG
SCM612
4
12.5 Carrier Selection
C
M S
e
a n u a l le c t i o n
A
P
r io
r it y
S
a r r i e r e le c t io n
A S
u t o m a t ic e le c t io n
S i n g le s s ig n m
C
o s t s
C o n t i n u o u s e n tM o v e
B
u
s i n e
s s
FS r he a i gr eh t
E
x c h a n
S AP A G 2002
Carrier selection provides a number of methods that are used to assign a carrier to a shipment: Manual Selection: A carrier is assigned to the selected shipments manually. Automatic Selection: This process can be performed interactively or in a background process using a Carrier Selection profile to direct the assignment of the carrier to shipments. If only one carrier is available for selection for the transport (only one carrier is maintained for the transportation lane), this carrier is assigned (single assignment). In the continuous move scenario a carrier is selected to provide transportation services for more leg in a transportation itinerary. In a continuous move the selected carrier transports goods to a location and then picks up goods to transport to another location(s). The checks for single assignment and continuous move occur before the selection strategies of the Carrier Profile are taken into account.
(C) SAP AG
SCM612
5
g e
12.6 Manual Carrier Selection
2. Carrier Selection
1. Selection
3. Enter Carrier
SAP AG 2002
In manual carrier selection, the following steps apply: Select the planned shipment(s) Select the Carrier Selection button Enter the Carrier in the dialog box If a carrier is selected manually, one or more shipments have to be selected using the Shipment view. You can also perform Carrier Selection by clicking the right mouse button and choosing Carrier selection. You can assign a carrier directly without checking or, after selecting a carrier selection profile, you can select according to the strategy defined in the profile. A carrier is removed from a shipment by selecting the shipment and then clicking the right mouse button and selecting Remov. carrier.
(C) SAP AG
SCM612
6
12.7 Automatic Carrier Selection
2. Carrier Selection
1. Select Shipment
4. Select Log
3. Enter Carrier Selection Profile
SAP AG 2002
Use a Carrier Profile with automatic carrier selection to direct the system when determining the shipment’s carrier. Select the log option when automatic carrier selection is used.
(C) SAP AG
SCM612
7
12.8 Carrier Profile Defines Run/Selection Boundaries
Model/Version
Time Horizon (for selection of shipments)
Locations
Vehicles
Transportation Mode
Selection Criteria (4)
SAP AG 2002
All selected shipments will get a carrier according to the carrier selection profile when using automatic Carrier Selection from interactive planning. You can also perform automatic carrier selection as a background process.
(C) SAP AG
SCM612
8
12.9 Carrier Profile: Carr.sel.
The Demand Horizon section is only used in background processing
Maximum optimizer runtime SAP AG 2002
In the Carr. Sel tab: The Planning version is entered. Fields in the Demand Horizon section are only used in automatic carrier selection in background processing. Demand Horizon in the Carrier Profile does not have to be the same as the Demand Horizon in the Optimization Profile. The Carrier runtime is the maximum amount of time, in seconds, that the optimizer is to use in selecting a carrier.
(C) SAP AG
SCM612
9
12.10 Carrier Profile: Planning Data
These fields are relevant only for background processing
SAP AG 2002
In the Planning data tab: Use Selected source location to select the shipments for background carrier selection based on the source location of the shipments. Use Means of Transport to select shipments in background carrier selection processing, based on the Transportation Method assigned to the vehicle resource assigned to the shipment by the optimizer.
(C) SAP AG
SCM612
10
12.11 Carrier Profile: Selection criteria
Order in which strategies are used
R/3 System Costing
Use Transportation lane costs
SAP AG 2002
Use the Selection strategies to direct the optimizer in choosing a carrier for the selected shipments. Use any or all of them in carrier selection. When using the Costs or Business Share selection strategies, you must select a cost location; either costs from the R/3 System (OLTP) (external costs) or costs stored in the transportation lane (internal costs).
(C) SAP AG
SCM612
11
12.12 Selection Strategies
Selection criteria for choosing a Carrier is ranked according to any combination of the following:
Priority (assigned to Carrier by lane and type/method)
Business Share (quota arrangements between Carriers)
Freight Cost (internal costs or actual costs calculated by the execution system)
Freight E xchange (Internet exchange for bidding)
SAP AG 2002
Costs: The carrier is selected by determining the least total cost for the shipment. The costs are determined by using either the internal costs defined in the Carrier data assigned to the Transportation Lanes or external costs by querying the transportation freight costs in the R/3 System Logistics Execution application. The total cost is determined for each carrier that has rates set for the shipment’s transportation lanes or from the external system. Priority: The carrier is selected by the highest priority on the lane of transportation. The priority is stored on the transportation lane by carrier. Business Share: The carrier is selected based on the business share maintained for the carrier. The percentage of shipments each carrier receives for a time period (day, week, and month) is based on the maintained percentage on the transportation lane. The actual values come from the maintained planning book. Private/Public Exchange: Private/Public Exchange is possible in the R/3 System. Enter a carrier in APO. The necessary information for the Private/Public Exchange is in the R/3 System..
(C) SAP AG
SCM612
12
12.13 Functionality of Automatic Carrier Selection
Priority Explicit priorities
Single Assignment
Costs
Onl y one c arrier to choos e
Inter nal Costs (Lane) External Costs (R/3)
Continuous Move
Business Share Maintained on Lane
Freight Exchange Private/ Public Exc hanges (R/3)
1. Level
2. Level
SAP AG 2002
Remarks for the use of external costs: To determine the costs maintained in the R/3 System the transportation planning point must be maintained. A default shipping point must be maintained in the R/3 System. In the table /SAPAPO/VS_ECUST the flag CS_EXT_COST_SKIP can be set. Before doing this, review OSS note 501352!
(C) SAP AG
SCM612
13
12.14 Strategy of the Direct Lane
Carrier 4
Point A Plant
Carrier 4
Carrier 3
Carrier 3
Carrier 2
Carrier 2
Carrier 2
Carrier 1
Carrier 1
Carrier 1
Point B Customer
Point C Customer
Point D Customer
Carrier 5 Carrier 2 Carrier 1 SAP AG 2002
Example: A transport travels from A via B and C to D. The system checks which transportation service providers cover all sections of the transport (A to B, B to C, C to D). The strategy of the direct lane (A to D) is then applied for the possible carriers.
(C) SAP AG
SCM612
14
12.15 Intra-zone Lanes and Carrier Selection
A transportation service provider can also be maintained for a transportation relationship of thi s kind. This intra-zone lane is only taken into account if the transport travels only within the transportation zone. It is not taken into account in these two case s:
If a carrier comes against an external transportation zone,it is assumed that it also runs within the transportation zone.
If a carrier leaves a transportation zone and goes external, it is assumed that it also runs within the transportation zone.
Intra-zone lane
SAP AG 2002
(C) SAP AG
SCM612
15
12.16 Continuous Move
Carrier 2
Carrier 2
Carrier 1
Carrier 1
Consideration of m aximum
SAP AG 2002
The Continuous Move setting manages whether a carrier arriving at a point of destination after having finished a shipment accepts a complete new shipment, starting from this point of destination. Requirements: • The previous shipment has to be assigned to the respective carrier. • When there are two or more carriers to select, the assignment is done by selection criteria (without consideration of the minimum). Settings for Continuous Move: APO: SAP Menu: Master Data → Location → Location; Tab Carrier
(C) SAP AG
SCM612
16
12.17 Quotation of Shipments
Priority Minimum - Maximum Single Assignment Maximum is considered
Costs Minimum - Maximum
Continuous Move
Business Share
Maximum is considered
- Quotation has to be maintained - Actual Values - Allocation of Minimum is at optimal costs
Minimum - Maximum
Selection criteria Costs > Selection criteria Business Share
1. Level
2. Level
SAP AG 2002
The allocation of quotas is above the selection strategies of the carrier selection profile. The strategies always occur under consideration of the allocations. For the Business Share strategy the allocation must be maintained. Actual values are required! During allocation, the following characteristics are used: Transportation allocation object Start location Target location Carrier Means of transport The following key figures are used: Maximum Minimum Actual value The maximum of the maintained allocation of quotas is taken into account during the manual assignment of a carrier.
(C) SAP AG
SCM612
17
12.18 Business Share Configuration
To use the Business Share Carrier Selection strategy: 1.
Create a Planning Area and Planning Book in Demand Planning
2.
In TP/VS Carrier Selection customizing: a. Create a Product Allocation Object, Group, and Procedure b. Assign the Product Allocation Procedure to the Planning Area
3.
Assign the Product Allocation Procedure to the Carriers
4.
Perform the initial load of the Min-Max number of shipments data for each carrier from the transportation lanes
SAP AG 2002
The Business Share carrier selection strategy is based on the number of carrier shipments. A minimum and maximum number of shipments that a carrier can tender is the basic selection criteria. Customizing activities create in APO a way to track the number of shipments a carrier has made in a time period. The time period is configurable (day, week, or month). The minimum and maximum number of shipments are set for a carrier within a transportation lane, by transportation method.
(C) SAP AG
SCM612
18
12.19 Vehicle Scheduling Process Flow (5) Configuration
Master Data
Modeling
Optimization (Load Consolidation & Vehicle Schedul ing)
Create/Transfer Shipments
Backorder Processing
Create/Transfer Deliveries
Carrier Selection
Carrier Tendering
Releasing Shipments
SAP AG 2002
(C) SAP AG
SCM612
19
12.20 TP/VS Tendering
EDI
Business Scenario: Internet Tendering
Create Shipment Publish
Transportation Planner Release for Execution
Business Scenario: Internet Tendering XML
Front end
View
Front end
HTML
Service Agent
Accept / Decline
SAP AG 2002
Collaborative Transportation Planning between shippers and their carriers allows both partners to streamline work processes and ultimately benefit from reduced handling costs, greater transparency, and efficiency. Shippers can inform their carriers about their shipment plans, and the carriers can accept, reject or change shipment requests. For example, the carrier could suggest an alternate pickup or delivery date. This process begins after all the prerequisites are fulfilled. Tendering is possible via EDI, fax, Internet, or a similar method of communication. Once planned shipments are released in APO, a tendering announcement is created.
(C) SAP AG
SCM612
20
12.21 Collaborative Transportation Planning: EDI CARRIER
SHIPPER
Transportation Planner
3
Review offered shipments
Transportation Planner
Se nd
4 Ac ce pt
Carrier Carrier system system
or d
off er s
en y
to
off er s
5 ca rri er
via
via
ED I
ED I
Execution if offer accepted
Alert if offer denied
APO APO TP/VS TP/VS
2
1 5
Vehicle Scheduling
R/3 R/3
SAP AG 2002
The transportation planner executes shipment planning using APO TP/VS and makes a carrier selection, either manually or via a VS optimization run. A shipment request is sent to the carrier via EDI using IDOC PLNSHP. The carrier reviews the request and either accepts or rejects it via EDI. The carrier can also change a pickup or delivery date and time for each stage of the shipment request. If the shipment request was rejected or modified, the shipper’s transportation planner is notified via the APO Alert Monitor. The planner can then select another carrier via carrier selection. If the shipment request was accepted, APO TP/VS issues a shipment order for execution in the R/3 System.
(C) SAP AG
SCM612
21
12.22 Bidding Alerts
Proposed delivery date changed by external carrier
Proposed shipment declined by external carrier
Proposed delivery date already in execution changed by external carrier
Proposed shipment already in execution declined by external carrier
SAP AG 2002
Bidding Alerts are generated during the tendering process between APO TP/VS and external carriers. After the APO VS run, the shipment proposals are transmitted to external carriers. Sometimes they are transmitted to the execution system (R/3) before confirmation from the external carrier arrives. In this case,, the system also triggers an execution system alert if there is a change or a rejection. Configure Bidding Alerts using the Alert Monitor. They are configured in the VS Alert Profile.
(C) SAP AG
SCM612
22
12.23 New tendering process after declination
SAP AG 2002
You can get an alert after declination of a shipment. Right-click on the generated alert and you can offer this shipment to a new carrier or to the same carrier who was previously chosen.
(C) SAP AG
SCM612
23
12.24 Collaborative Transportation Planning: Internet CARRIER
SHIPPER
Transportation Planner
Transportation Planner
2 3 Review offered shipments
Internet
3
Inf
orm
ca rri er
5 ( vi
a e- m 4 Accep ail t or ) den y off e Get shipment rs
Alert if offer denied
APO APO TP/VS TP/VS
details via XML
1 Carrier Carrier system system
Execution if offer accepted
5
Vehicle Scheduling
R/3 R/3
SAP AG 2002
The transportation planner at the shipper’s site plans shipments using APO TP/VS and makes a carrier selection, either manually or via a VS optimization run. The planner then sends a hyperlink via e-mail to a Web page with the current shipment requests. The carrier reviews the shipment requests in the Internet and either accepts or rejects them. The carrier can also change a pickup or delivery date and time for each stage of a shipment request. Furthermore, the carrier can display an XML file with all details of the shipment request by clicking on the shipment number. The XML file can be displayed in a carrier-specific layout that is maintained in the APO partner settings. If a shipment request was rejected or modified, the shipper’s transportation planner is notified via the APO Alert Monitor. The planner can then select another carrier via carrier selection. If the shipment request was accepted, APO TP/VS issues a shipment order for execution in the R/3 System. Tendering can occur automatically or at the discretion of the shipper, but only after the shipment is released in APO. Collaboration for Tendering via the Web requires an Internet Transaction Server (ITS) with the Collaborative HTML Templates installed
(C) SAP AG
SCM612
24
12.25 Collaboration Configuration (Tendering)
Three Step Process 1) Create a Collaboration Partner Identify Carrier 2) Set Communication Settings Application Type (Transportation Planning) E-Mail Activation/Information XML Indicator/Stylesheet 3) Assi gn Users to Collaboration Partner Identify System Users
SAP AG 2002
(C) SAP AG
SCM612
25
12.26 Shipment Details in a Carrier-Specific Layout
The following customizing settings are relevant to view the XML file with the shipment details in the transportation collaboration scenario : 1.
Maintain a collaboration partner and assign the user of the external transportation partner to this partner (transaction /SAPAPO/CLP_SETTINGS).
2.
Maintain the collaboration scenario Transportation Planning for this partner. Make sure, that you selected the XML Displayed Activated indicator.
3.
As the XML file is based on shipment information derived from the IDOC PLNSHP, complete your customizing with the necessary settings for the EDI scenario for Collaborative Transportation Planning.
SAP AG 2002
Note: The IDOC generation is only required for the XML display. In the IDOC partner profile (transaction /WE20) you should define a receiver port with a physical directory located on your own application server. There is a default XSLT stylesheet that can be modified by the customer in the directory ../MIMES/CLPGLOBAL/99/STYLE/plnshp.xsl. The URL for the XML style sheet is: http://
:/sap/ist/mimes/clpglobal/99/style/plnshp.xsl
(C) SAP AG
SCM612
26
12.27 Carrier Selection: Unit Summary
You are now able to: Make the required customizing settings related to carrier selection Perform carrier selection for planned shipments
SAP AG 2002
(C) SAP AG
SCM612
27
12.28Exercises Unit: Carrier Selection Topic: Carrier Profile At the conclusion of this exercise, you will be able to: •
Create a Carrier profile and use it to perform carrier selection.
After the planning of one or more shipments, carrier selection can be performed to either manually or automatically assign a carrier to each shipment. In the project role, you must test this function.
1-1
Three carriers have already been created in APO for your use: 0000001058 0000001925 0000001930 The first thing you must do is assign the carriers to the transportation methods in the transportation lanes where they will be used. 1-1-1 Assign these carriers to your transportation methods: FTL## and LTL## in transportation lanes: 12## → T-S11B## 12## → T-S11C## Set the internal costs of the carriers as follows: Carrier: 0000001058 LTL rate is .900 per KM Carrier: 0000001058 FTL rate is .750 per KM Carrier: 0000001925 LTL rate is .850 per KM Carrier: 0000001925 FTL rate is .800 per KM Carrier: 0000001930 LTL rate is .800 per KM Carrier: 0000001930 LTL rate is .750 per KM
1-2
Create a Carrier Selection Profile: Use the following settings to create your profile: Carr. profile: GR## Description: Carrier Selection Gr. ## Planning version: 000 Under the Carr. sel tab:
(C) SAP AG
SCM612
28
Set the Fixed Horizon: Start date: Today's Date Time: 00:00:00 End date: Today's Date + 8 weeks Time: 23:59:00 Carrier runtime: 60 sec. Under the Planning data tab: Set All locations Set All vehicles Under the Sel. criteria tab: Set the Selection strategies as follows: Priority: Leave blank Costs: 1 Select: Internal costs Business Share: Leave blank Freight exchange: Leave blank Choose Save. 1-3
Create two sales orders: Sales Document Type: OR Sold-to: T-S11B## P.O.Number: 13-1-## Requested Del. Date: Today + 3 weeks Material and Qty: T-ATD2-## 100 PC Document Number: _______________________ Sold-to: T-S11C## P.O.Number: 13-2-## Requested Del. Date: Today + 3 weeks Material and Qty: T-ATD2-## 50 PC T-ATD3-## 50 PC Document Number: _______________________
(C) SAP AG
SCM612
29
1-4
Run the Interactive Vehicle Scheduling for the sales orders. How many shipments were created? _______________________ 1-4-1 Select each shipment created and perform Carrier Selection using your Carrier Selection profile, GR##. 1-4-2 What carrier was assigned to the order for T-S11B##? ___________________________________________ 1-4-3 What carrier was assigned to the order for T-S11C##? ___________________________________________
1-5
Freight rates have been set up in the R/3 System for the three carriers. Change your Carrier Selection profile to selct the carriers based on "External" costs. 1-5-1 Change your CS profile, GR##. 1-5-2 Return to Interactive Vehicle Scheduling and select the planned shipments that were created in 1-4 and perform Carrier Selection. Select the "log" option on the selection screen. Did the results of the carrier selection change? ____________ In the Appendix is a copy of the freight rates established in the R/3 System. Use them to verify that the correct carrier was selected.
(C) SAP AG
SCM612
30
12.29Carrier Selection Solutions Unit: Carrier Selection Topic: Carrier Profile 1-1
Update the Transportation Methods within the transportation lanes with the carrier information: APO SAP Menu → Master Data → /SAPAPO/SCC_TL1 - Transportation Lanes 1-1-1 Update each transportation lane: Model name: 000 Source loc.: 12## Target loc.: T-S11B## Select Change. In the means of trans. section, select your FTL##. Select the Carrier assignment icon (the truck) in the toolbar. The bottom section of the screen will now become the Carrier for transport type FTL## area. Select the Creation of new entry icon in the toolbar. The Carrier detail box will open up on the right side of the screen. You might have to resize the left side of the window to see all of the data fields in the detail box. Create the carrier entry: Enter the Carrier location number. Enter the rate for the carrier in the Carrier costs (per KM) field. Select Copy at the top of the screen. Enter the second and third carriers for the Transportation Method. After completing the entry for the third carrier, select Copy and close. Select the next Transportation Method, LTL## and repeat the process for the carriers and their rates for this method. Choose Save after all data has been entered for the lane. Perform this process for the next transportation lane.
1-2
Create your Carrier Selection profile. APO IMG: → Advanced Planner and Optimizer (APO) → Transportation Planning/Vehicle Scheduling (TP/VS) → Carrier Selection → Define Carrier Profile Enter Carr. profile:
GR##
Select Create. (C) SAP AG
SCM612
31
Enter the Carrier Profile Description:
Carrier Selection GR. ##
Carr. sel. tab: Planning Version:
000
Enter Horizon (fixed) dates data. Set the Carrier runtime: 60 Planning data tab: Make no entries here. Sel. criteria tab: Set the Selection strategies as follows: Priority: Leave blank Costs: 1 Select: Internal costs Business Share: Leave blank Freight exchange: Leave blank Choose Save. 1-3
Create two sales orders: R/3 SAP Menu: Logistics → Sales and Distribution → Sales → Order → VA01 – Create Enter the two sales orders based on the data in the Exercises section. After saving a document, record its number in the Exercise section.
1-4
Run the Interactive Vehicle Scheduling for the sales orders: APO SAP Menu → Transportation Planning/Vehicle Scheduling → Planning → /SAPAPO/VS01 - Interactive Vehicle Scheduling On the Vehicle Scheduling – Selection screen, select your variant OPOUT-18 by selecting the Get variant... icon. Select Execute. Lock all sales/delivery documents except the two that you just created. To Lock a sales/delivery document, select it, then select the Do not optimize order icon (it's the padlock). Select VS Optimizer. Select Execute Optimization. After the optimization run completes: Select Confirm. Select Shipments in the shuffler. Select one of the shipments created for your sales orders by double-clicking on it. Select Carrier selection in the application toolbar. When the Carrier Profile dialog box displays, enter your Carrier Selection profile and select the Log checkbox. Select Execute.
(C) SAP AG
SCM612
32
After a few seconds, you should get a message Carrier selection completed successfully. Double-click on the shipment for which carrier selection was just performed. Select the Details tab on the right-side of the screen and find the assigned carrier. Repeat the carrier selection process for the remaining shipment related to your second sales order. 1-5
Modify your carrier selection profile to use the external costs in the R/3 System and rerun carrier selection for your two shipments: 1-5-1 Update your carrier profile: APO IMG: → Advanced Planner and Optimizer (APO) → Transportation Planning/Vehicle Scheduling (TP/VS) → Carrier Selection → Define Carrier Profile Enter Carr. profile:
GR##
Select Change. Select the Sel. criteria tab. In the Costs selection strategy, select External costs. Choose Save.
(C) SAP AG
SCM612
33
1-5-2 In interactive vehicle scheduling, rerun your carrier selection and review the results. APO SAP Menu → Transportation Planning/Vehicle Scheduling → Planning → /SAPAPO/VS01 - Interactive Vehicle Scheduling On the Vehicle Scheduling – Selection screen, select your variant OPOUT18 by selecting the Get variant… icon. Select Execute. Select Shipments in the shuffler. Select one of the shipments created for your sales orders by double-clicking on it. Select Carrier selection in the application toolbar. When the Carrier Profile dialog box displays, enter your Carrier Selection profile and select the Log checkbox. Select Execute. After a few seconds, you should get a message Carrier selection completed successfully. Double-click on the shipment for which carrier selection was just performed. Select the Details tab on the right-side of the screen and find the assigned carrier. Repeat the carrier selection process for the remaining shipment related to your second sales order.
(C) SAP AG
SCM612
34
13 TP/VS: Additional Topics
Contents: Backorder Proce ssing (BOP ) Shipment and Transportation Scheduling Shipment scheduling
SAP AG 2002
(C) SAP AG
SCM612
1
13.2 TP/VS: Additional Topics : Unit Objectives
At the conclusion of thi s uni t, you will be able to: Explain the Back Ordering process and its effect on TP/VS planning Explain the Shipment and Transportation Proce ss Explain the forms of scheduling related to TP/VS
SAP AG 2002
(C) SAP AG
SCM612
2
13.3 TP/VS: Additional Topics : Business Scenario
Some functions that can play a role in the planning process repre sent proce sse s that supplement TP/VS. Some functions and features may be optional and not required by every customer.
SAP AG 2002
(C) SAP AG
SCM612
3
13.4 Backorder Rescheduling/ Processing
What Does It Do? It iss a redistribution of the available quantity of one or more products using selected orders. Previous confirmation of the orders involved are ignored and added to the available quantity during rescheduling
Why Does It Effect Transportation Planning? Redistribution of previously confirmed order quantities may change the proposed delivery of Planned Shipments generated by Vehicle Scheduling
SAP AG 2002
Backorder processing is essentially set to process entered requirements and to diagnose and cancel backorder situations. A backorder situation can require the changing of confirmed quantities or dates After a changed availability situation After the arrival of priority orders After a planning run in PP/DS or in SNP After changes in the location-specific product master data for ATP The Backorder Processing (BOP) plays an important role within the Transportation Management Solution for the Sales Order Fulfillment Process: when running BOP on sales orders which have been consolidated previously by TP/VS, the scheduling is based on the given loading dates. With the update of the orders into the R/3 System, the documents have the correct dates and times as defined by the shipments activities. BOP is only possible for Sales Orders.
(C) SAP AG
SCM612
4
13.5 Backorder Processing and Scheduling (1) A Monitor
Alert Filter
Individual
Filter
PP/DS
TP/VS Load. Activity
SNP
Master Data
NetChange Filter
SORTER: Using Priorities Backorder Proce ssing (Batch) Backorder Proce ssing (Interactive) • Simulation • Interactive Post Processing • Posting of Results to R/3 or Legacy System SAP AG 2002
Two functions are available for processing backorders in SAP APO: Batch Backorder Processing Interactive Backorder Processing Batch BOP corresponds essentially to rescheduling in the R/3 System, though with enhanced features: The filter can be configured The sort can be configured The scheduling can be configured Backorder processing is used in Vehicle Scheduling to transfer data changed in Transportation Planning back to SAP R/3. Transportation Planning must be based on the requested quantity and the requested date. Process: (BOP → ) TP/VS → BOP → Delivery
(C) SAP AG
SCM612
5
13.6 Backorder Processing and Scheduling (2) Filter
Alert Filter - All orders with:
Production Planning and Detailed Scheduling
Net-Change-Filter - All orders changed through:
Available To Promise
Production Planning and Detailed Scheduling Supply Network Planning runs
Filter: There are 15 criteria to set up a filter:
Product Location Order creation date And so on
Transportation Planning and Vehicle Scheduling: External loading activities are considered SAP AG 2002
(C) SAP AG
SCM612
6
13.7 Backorder Processing and Scheduling (3) Sorter
The sorter is prioritizing the selected / filtered orders
There are 15 priorities, including:
Product Location Delivery prioritiy And so on
Backorder Proce ssing
Interactive/Batch planning job
Can read ATP Customizing (Check mode, and Allocation procedure)
Horizons for rescheduling
Basic methods selection
Rules selection can be switched off
SAP AG 2002
(C) SAP AG
SCM612
7
13.8 ATP and Transportation Planning Allocations for Transports
Local MS
*
Backorder Processing via external Loading Activities
Global APO
Local SCE
**
Mat. Availability time
ERP Pick/Pack
Loading time
Load
GI time
Transit
Transport Dispo
Delivery time
UnLoad Mat. Availability time
Transport Disposition Time
* MS = Manufacturing System **SCE = Supply Chain Execution System
SAP AG 2002
(C) SAP AG
SCM612
8
13.9 Direct Update of Batch BOP
Filter
Sort
Rejection of the confirmed quantities
ATP check
New date/quantities
The results are always held in a buffer.
SAP AG 2002
Process: Carry out batch backorder processing to redistribute previously-confirmed quantities for the order items of backorders, according to a list of priorities As long as the update in the connected OLTP system is not yet completed, the assigned quantities are protected in APO as temporary quantity assignments. The changes are updated in the R/3 System. The update is confirmed to APO. You can delete the results in the buffer. These are only used as a log. If you have to define unforeseen short-term sales priorities, use interactive backorder processing
(C) SAP AG
SCM612
9
13.10 Batch BOP with Postprocessing
Manually redistribute confirmed quantities of one or more products
Access via the Product View
Processing occurs at schedule line level
Dates of schedule lines can be changed, deleted, or created
Role : ATP Controller
SAP AG 2002
Purpose: You do not want to update the results of backorder processing directly, you want to carry out an operative simulation first. Prerequisite: Maintain the settings for backorder processing and have orders in APO. Process: Set the parameter Execution mode with postprocessing on the tab page and carry out backorder processing. The results are not updated immediately; rather, they are saved in a buffer. Call the results display to process the results. The assigned quantities are protected by temporary quantity assignments. You can process the results via interactive backorder processing from the results list. You can update or reject the results afterwards. If necessary, delete the results list or the results in the buffer.
(C) SAP AG
SCM612
10
13.11 Shipment and Transportation Scheduling Shipment Scheduling All processe s that are necessary to initiate goods shipment are included in shipment scheduling. These processe s include loading, picking, and packing. Shipment scheduling determines the material availability date and loading start. Transportation Scheduling All deadlines that affect shipment preparation and execution are included in transportation scheduling. These include transportation lead time, transportation time, and the unloading/loading time (for stock transfers). Transportation scheduling use s the requested delivery date to determine the goods i ssue deadline and the transportation planning deadline. The possible delivery date is determined if the system use s forward scheduling.
SAP AG 2002
You can specify a requested delivery date for each schedule line in an item when you enter an order. The customer should receive the goods by this date. During order processing, the system can automatically plan when the necessary shipment activities such as picking, loading, and transportation must begin in order to stay on schedule for the requested delivery date. The system starts with the requested delivery date and schedules chronologically backwards. For this reason, this process is called backward scheduling. The system determines the deadlines as follows: Requested delivery date – transportation time = Goods issue deadline Goods issue deadline – loading time = loading start The planning date and the material availability date are determined based on the loading start. Loading start – planning lead time = planning date Loading start – pick/pack time = material availability date If the system recognizes that the material availability date or the planning date fall in the past, it automatically runs forward scheduling in order to determine a delivery date that can be confirmed. Note: If there is no material available on the material availability date, the SAP system can run an availability check according to the system settings. The resulting material availability date is then used as a basis for forward scheduling. Note: In a rules-based availability check, backward scheduling is carried out to determine the material availability date for a location/product substitution, starting from the original requested delivery date. This is necessary, since the substitution can influence the scheduling result (for example, because of another transportation lane in location determination). Note: For scheduling to occur properly, the transportation zones and shipping conditions must be copied from the SAP R/3 System into the SAP APO system.
(C) SAP AG
SCM612
11
13.12 Scheduling Process
APO
R/3 Plug-In Creat e sales order Material Material (Plant APO (Plant relevant) not APO relevant)
Deter mine process durations (cond.)
Call scheduling
Calculate dates and times
Calculate dates and times
Call ATP
Check ATP
Deter mine process durations
Deter mine process durations
Calculate dates and times
Delete temporary quantity assignments
Deter mine process durations
Calculate dates and times
Save sales order
SAP AG 2002
Start the process by creating a sales order. Enter the requested material, quantity, and delivery date. The R/3 System uses the order type to determine whether shipment scheduling or transportation scheduling should be carried out. The following points are valid for order types for which scheduling is requested. The R/3 System determines the plant for the material in each item. The CIF integration model defines whether the availability check in the APO system is to be run for materials in this plant. If this is the case, scheduling can also occur in the APO system. Note: You mix items within a sales order whose availability is checked in the APO system and in the R/3 System: Due to the various scheduling techniques, there can be considerable deviations between the times calculated (the transit time, in particular). Functions involving several items, such as complete delivery and delivery groups, are especially susceptible to such detrimental effects. The material availability date is calculated either in the APO system or in the R/3 System for the requested delivery date of an item. The system checks availability for material, plant, and quantity on the material availability date. R/3 System or APO system: If the material availability date that was determined previously cannot be confirmed, the system redetermines the process duration, recalculates the dates and times, adds more schedule lines, and returns this information to the R/3 System. This normally occurs when availability is found to be insufficient or when the material availability date lies in the past. Save the sales order.
(C) SAP AG
SCM612
12
13.13 Schedules 1. Create a Transport Method (flag for Schedule has to be set) 2. Create a Vehicle Resource 3. Assign Vehicle Resource to Model/Planning Version 4. Assign Transport Method to Transportation Lane 5. Maintain Vehicle Scheduling Costs for Transport Methods 6. Maintain Itinerary 7. Assign Itinerary to active Model 8. Maintenance from here on for Scenario 1 or Scenario 2 Scenario 1: Departure at a fixed day of the week (for example, every Monday) Scenario 2: Departure in a predefined rhythm (for example, every 10 days)
SAP AG 2002
IMG: Advanced Planner and Optimizer (APO) → Supply Chain Engineer (SCE) → Maintain Transport Method Relevant fields for maintenance of schedules are: Vehicle (= Transport Method), Transportation Mode. and Schedule. SAP Menu: Master Data → Resource; Tab Vehicle The Schedule flag has to be set for the Vehicle Resource you have maintained at number one. Is done in the Supply Chain Engineer (SCE) or in Create-View of Resource Master Data. SAP Menu: Master Data → Transportation Lanes or SAP Menu: Master Data → Supply Chain Engineer → Maintain Model The whole transport duration should be maintained here. To calculate the time of arrival, the transport duration is added up to departure time. SAP Menu: Master Data → Master Data for Transportation Planning/Vehicle Scheduling → Maintain Vehicle Scheduling Costs SAP Menu: Master Data → Master Data for Transportation Planning/Vehicle Scheduling → Schedules → Maintain Itinerary SAP Menu: Master Data → Master Data for Transportation Planning/Vehicle Scheduling → Schedules → Maintain Itinerary (Initial Screen)
(C) SAP AG
SCM612
13
13.14 Schedules (Scenario 1)
1. Maintain Calendar 2. Maintain Schedule Validity Period 3. Maintain Schedule
SAP AG 2002
IMG: General Settings → Maintain Calendar - Factory Calendar - Select Change - Create a new calendar - Enter Factory calendarID, name of calendar, Validity, and so on - Choose workdays which are relevant for departure - Save SAP Menu: Master Data → Master Data of Transportation Planning/Vehicle Scheduling → Schedules → Maintain Schedule Validity Period - Press New Entries - Enter a name - Identify the calendar by enter the CalendarID - Maintain Validity SAP Menu: Master Data → Master Data of Transportation Planning/Vehicle Scheduling → Schedules → Maintain Schedule - Enter a name - Select Create - Enter Validity, Itinerary, Transportation Method, and name of Schedule Vehicle Resource - Enter time of departure and departure day - Choose Generate to create departure times and days on the basis of the maintained factory calendar - The respective calendar has to be maintained to change departure times.
(C) SAP AG
SCM612
14
13.15 Schedules (Scenario 2) 1. Maintain Calendar 2. Maintain Schedule Validity Period 3. Maintain Schedule; departure times have to be maintained manually
SAP AG 2002
IMG: General Settings → Maintain Calendar - Factory Calendar - Press Change - Create a new calendar - Enter Factory calendarID, name of calendar, Validity, and so on - Choose workdays which are relevant for departure - Save SAP Menu: Master Data → Master Data of Transportation Planning/Vehicle Scheduling → Schedules → Maintain Schedule Validity Period - Press New Entries - Enter a name - Assign a calendarID - Maintain Validity SAP Menu: Master Data → Master Data of Transportation Planning/Vehicle Scheduling → Schedules → Maintain Schedule - Enter a name - Press Create - Enter Validity, Itinerary, Transportation Method and name of Schedule Vehicle Resource - Enter departure times manually - To change departure times, the respective calendar has to be maintained
(C) SAP AG
SCM612
15
13.16 Schedules
When using Schedules in the Optimization, note the following: Loading/Unloading schedule vehicles is always estimated at zero. Do not maintain any work breaks for schedule resource s. Maintain calendars with seven working days per week for schedule resource s. Opening hours maintained for schedule-relevant locations can result in you not being able to use the schedule resource if the opening hours do not corre spond to the arrival/departure times.
SAP AG 2002
The travel time maintained in the schedule and the transport connections apply to the resource that is assigned to the schedule. Schedule A → B → C: Departure from location A at 10:00 Duration A → B: three hours, duration B → C: two hours Arrival at B at 13:00; at C at 15:00
(C) SAP AG
SCM612
16
13.17 TP/VS: Additional Topics : Unit Summary
You are now able to: Explain the Back Order process and its impact on TP/VS planning Explain the Shipment and Transportation Proce ss Define the forms of scheduling in TP/VS
SAP AG 2002
(C) SAP AG
SCM612
17
14 TP/VS - Monitoring
Contents: An overview of transportation content in BW An overview of Supply Chain Event Management (SCEM)
SAP AG 2002
(C) SAP AG
SCM612
1
14.2 TP/VS – Monitoring: Unit Objectives
At the conclusion of thi s uni t, you will be able to: Understand the ba sic reporting functionalties in BW Understand the additional available management tools in transportation planning
SAP AG 2002
(C) SAP AG
SCM612
2
14.3 TP/VS – Monitoring: Business Scenario
The PC electronics manufacturer use s the BW Key Performance Indicators (KPI s) a s benchmarks to measure transportation planning performance.
SAP AG 2002
(C) SAP AG
SCM612
3
14.4 SAP BW-Definition SAP Busine ss Information Warehouse ...
... is a collection, combination, and consolidation of information, which supports further theme-orientated analysi s. ... delivers data to all enterprise Front-end-system s to support the decision proce ss for employees and managers. ... is physi cally separated from the datasources of the OLTPSystem and build up the connection to the OLTPsystem or any other data-providing-system for the purpose of periodic full-data or delta-data upload.
SAP AG 2002
(C) SAP AG
SCM612
4
14.5 Positioning of BW within the SAP Environment
R/2 R/2 le leg gaacy cy 3 3rd rd Open pa rty pa Internet rty standard
nonmySAP.com 3.1H
Single Port Portaall sign- Industry-specific Industry-specific Coc on Cockk-ro role leba base sed d pit pitss pe lize perrso sona na lized d Dra Drag g& &Re Rela lattee WorkingwithWeb-Browser
R/3 4.6 mySAP.com-Components FI FI LO LO SEM SEM HR HR CF CFM M KM KM
M Maarrkkeett-pla place ce
APO APO CR CRM M
B2 B2B B BW BW
Ente inside rpri s e fro nti er Pa Part rtne nerr outside
SAP SAP mySAP.comInternet Services
Other InternetServices SAP AG 2002
(C) SAP AG
SCM612
5
14.6 Main Topics of BW
Integration of information from different source systems (openarchitecture)
Stand-alone solution, with a very strong backend integration
A system that is easy to h andle for standard r eporting and multid imensional ad-hoc anal ysis (OL AP)
Single point of entry
All business content delivered by SAP BW is available in the Internet
Take the load off the operating system and relieve the IT-organization
High performance
Quick installation and maintenance
SAP BW Replaces the R/3 Reporting System
SAP AG 2002
(C) SAP AG
SCM612
6
14.7 BW-Architecture
SAP AG 2002
(C) SAP AG
SCM612
7
14.8 Data Process Chain Role Decision, prep aration
Workbook Report
Query Definition
Analysi s
InfoCube Update rules
Updating Transformation, Aggregation
Communication structure
InfoSource Extraction
Source system
Mapping & Transformationrules Transfer structure
Transfer structure
OLTP
Syn. Data Provider
SAP AG 2002
(C) SAP AG
SCM612
8
14.9 Possible Use of the Busine ss Content Roles
Standard Standard analysi analysis,s, “Ready-to-go “Ready-to-go solutions” solutions”
Web reports Workbooks
ive ct e sp er Queries P er s Best Practices U
InfoCubes ew Vi r e Us
InfoObjects
d In
Transfer rules InfoSources
d an t S
Customer Customer Order Order Entry Entry
d ar
id iv
is lys a n lA a u
n t io a z i
Standard Standard Content, Content, Ea sy to Extend! Ea sy to Extend! Maintenance Maintenancethrough through SAP SAP
Extractors SAP AG 2002
(C) SAP AG
SCM612
9
14.10 Transportation Content In BW: Overview
Transportation Content available in BW 2.0B Connection to the R/3 System for 4.0B and higher Infocube s:
Freight Cost Overview
Freight Cost Detail
Shipment Header
Shipment Stages
Delivery Data of the Shipment Stages
SAP AG 2002
(C) SAP AG
SCM612
10
14.11 Example: Freight Cost Reporting Overview (1)
Key figure s:
Characteristics from:
Net Value Freight Costs
Transportation Header
Stages
Freight Cost Item
Examples for Queries:
Freight Costs per Carrier
Freight Costs per Route
SAP AG 2002
(C) SAP AG
SCM612
11
14.12 Example: Freight Cost Reporting Overview (2)
SAP AG 2002
(C) SAP AG
SCM612
12
14.13 Logistics Content: Outlook
KPIs for Distribution, Warehousing, and Transportation KPIs for Measuring: Costs Cycle Time Service/Quality Assets SAP AG 2002
(C) SAP AG
SCM612
13
14.14 Definition of Supply Chain Event Management
“Supply Chain Event Management (SCEM) is an application that supports control processes for managing events within and between companies. It consists of a set of integrated software functionality that supports five business processes: monitor, notify, simulate, control, and measure supply chain activities.” AMR Research, January 2000
SAP AG 2002
The goals of Supply Chain Event Management are: Optimize information flow in the supply chain within enterprises and with their business partners Improve the overview of the current status of the whole supply chain of an enterprise Improve forecast ability for critical events within the supply chain, allowing faster reaction times Automatic reaction to incoming event messages using Workflow triggers and data progression in ERP systems
(C) SAP AG
SCM612
14
14.15 Types of Events and Tracking
Actual events Event 1
Event 2
Event 3
Event 2
Event 1 Regular event
Unexpected event
Event 4 Overdue event
Expected events Process milestones
Unreported event
SAP AG 2002
Tracking: Is gathering real time data for events, status, locations, and parties involved for elements in a logistics process Can be used for warnings, messages, data progression, or follow-up processes when:
Planned events occur Unforeseen events occur Planned events do not occur Shows a view of the current status and the history of a logistics objects (transport, container, and so on) More economical operations by using the better overview of resources and capacities of logistics partners Increases customer satisfaction through faster, more reliable service By releasing a shipment in APO TP/VS, an expected event for tendering this shipment is generated in the Event Manager.
(C) SAP AG
SCM612
15
14.16 SCEM Example: Procurement Process W arehouse Ordering Part y
RF RF Dev Device ice Goods Goods Receipt Receipt Quality QualityCheck Check Availability Availability
Inb. Del.
EDI EDI Departure Departure ETA ETA Arrival Arrival
EDI EDI Arrival Arrival Import Import Documents Documents Loading Loading Ship Ship
PO TO
Event Manager
EDI Incoming Order Scheduling Confirmation
Carrier
Carrier
Purchase Order
Transfer Order
S AP System
Singapore
Port of Departure
Pickup POD Inbound Deliv ery Warehouse
Scenario:
Internet Internet Loading Loading Departure Departure Border Border Crossing Crossing Arrival ArrivalPOL POL
Supplier
Internet Internet Incoming Incoming Purchase Purchase Order Order Start Start of of Production Production End End of of Production Production Goods Goods Issue Issue
Malaysia
An electronics manufacturer orders customer-specific semiconductors in Malaysia.
Added Value: The timely processing of the purchase order can be monitored. SAP AG 2002
SCEM can be used for whole processes. Procurement uses one single point of entry for its various documents Many parties send events to the Event Manager using different ways of communication,such as the Internet (Portals), EDI, Radio Frequency devices, and so on
(C) SAP AG
SCM612
16
14.17 SCEM Example: Tracking Pallets for Recall Loading Point
DC1
Customer A
ALERT ALERT !! Batch Batch on on PAL PAL 1,2,3 1,2,3 contaminated contaminated !!
Event Manager
DC3
Pick-up Pal.1,2,3
SAP System
Crossdock Pal 1,2,3.
Tracking Ev ents
Dispatch Pal 1 Dispatch Pal 2,3
Customer B
DC2
Crossdock Pal 2,3. Dispatch Pal 3
POD Pal 3
Locations Locations PAL PAL 1: 1: Shipped Shipped to to DC DC 11 PAL PAL 2: 2: In In DC DC 22 PAL PAL 3: 3: Deliver Delivered ed to to Customer Customer C C
Customer C
SAP AG 2002
Loading point and DC1 are managed by the vendor. DC2 and DC3 are third party managed. Here the process goes out of sight. Handling Unit Management produces good and creates tracking events. Tracking the pallets allows you to know where the pallets are at any given time.
(C) SAP AG
SCM612
17
14.18 SCEM Scenario Manufacturer Customer
Carrier
Start Production
Gets informed via e-mail and monitors production progress
Track Production
Process Operator starts production uses PI-Sheets and communication to process control
End Production Truck driver is informed about pick up time via SMS Load truck at dock Leave manufacturing site
Track Shipment Monitors shipment using web access
Confirms correct delivery of ordered ice cream
Warehouse employee confirmes loading completion ) Truck driver confirmes departure, delay, and arrival using car mounted device
Proof of delivery
SAP AG 2002
(C) SAP AG
SCM612
18
14.19 Embedded Status Reporting: Example
SAP AG 2002
(C) SAP AG
SCM612
19
14.20 A Few Application Scenarios for Event Management Proce Process ss Automation Automation
Recalculation Recalculation of of arrival arrival time time Production Production rescheduling rescheduling for for late deliveries deliveries Progressive Progressive run run times times Calculation Calculation of of demurrage demurrage Verification Verification of of completeness completeness of of the the process process steps steps
Informs Informs business business partners partners Displays Displays alarms alarms monitor monitor On Customer service On time time deliveries deliveries Sets Sets up up trouble trouble Average shooting Average run run time time shooting Uniform Uniform status status messages messages Last Last recorded recorded status status
Alarm Alarm
Valuation Valuation Supply Chain Event Management actively supports managing the logistics process of an enterprise as well as the business partners SAP AG 2002
(C) SAP AG
SCM612
20
14.21 SCEM: Scope and Integration Primarily used in transportation, but al so usedfor upstream and downstream processe s Supply Chain Event Management offers generic service s for creating, saving, proce ssing, and administrating status data from a supply chain process Supply Chain Event Management is completely integrated with mySAP.com Supply Chain Event Management supports all transport modes Road
Sea Air Rail Container Parcel SAP AG 2002
(C) SAP AG
SCM612
21
14.22 TP/VS – Monitoring: Unit Summary
You are now able to: Understand the ba sic reporting functionalties in BW Understand the additional available management tools in transportation planning
SAP AG 2002
(C) SAP AG
SCM612
22
15 Course Objectives
You are now able to: Use the TP/VS component of APO to plan both
inbound and outbound shipments Create the necessary integration models to
communicate data between an R/3 System and the APO TP/VS component Make the necessary customizing settings
required to perform transportation planning, vehicle scheduling, and carrier selection in the TP/VS environment De scribe the various monitoring tool s available to
TP/VS
SAP AG 2002
(C) SAP AG
SCM612
1
15.2 Recommended Follow-up Activities
Read on-line documentation Read IMG documentation Read release note s Read OSS Notes
SAP AG 2002
Here are some of the most important TP/VS OSS notes: 362445 Effects on document changes in the R/3 System on APO shipments 379846 Vehicle Scheduling Order Category Selection 388499 Use of transportation zones 392302 Collective note for Transportation planning 397475 Use of charging functions 415477 Customizing for XML details in APO Coll. Transportation 445118 Functions of selection of carriers 448487 Transportation Planning: Integration of the R/3 and APO systems 483257 Own and external Transportation Methods 514897 Collective notes about Performance Optimization in TP/VS Those notes are always updated.
(C) SAP AG
SCM612
2
16 Appendix
Contents: Carrier Rates for Carrier Selection Exercise APO-R/3 CIF Troubleshooting Guide Tips and Tricks for APO CIF OSS Note s
SAP AG 2002
(C) SAP AG
SCM612
1
16.2 Carrier Rates for Carrier Selection Exercise
SAP AG 2002
(C) SAP AG
SCM612
2
16.3Freight Rates: Condition Type: FB00 Key: Service Agent / TZ-Dep. / TZ-target Gross Weight Scale Id: 3
Rates per 100 KG 1058
Currency: EUR
0
500
1000
5000
10000
DE00-DE60
35
32
29
24
15
DE00-DE70
40
38
37
32
21
DE00-DE80
45
43
42
37
26
Cheaper: TL's
Rates per 100 KG 1930
0
500
1000
5000
10000
DE00-DE60
34
31
28
23
19
DE00-DE70
38
36
35
30
22
DE00-DE80
43
41
40
35
28
Cheaper: LTL's
Rates per 100 KG 1925
0
500
1000
5000
10000
Cheaper: DE70
DE00-DE60
37
34
30
26
20
DE80
DE00-DE70
35
33
32
27
19
DE00-DE80
41
39
37
33
23
(C) SAP AG
SCM612
3
16.4 Tips and Tricks for APO CIF
SAP AG 2002
(C) SAP AG
SCM612
4
16.5 OSS Note s
SAP AG 2002
(C) SAP AG
SCM612
5
