Page 1
SAP AG 1998 O4 SAP TechEd 98, Karlsruhe (Ottenstein) / 1
Michael OttensteinSAP AG
InterfacesMM-MOB and WM-LSR
SAP AG 1998 O4 SAP TechEd 98, Karlsruhe (Ottenstein) / 2
Contents
z Overview about MM and WM
z Interfaces WM-LSR and MM-MOB
z Application Scenarios
z Technical Aspects
z Customizing (System Demo)
Page 2
SAP AG 1998 O4 SAP TechEd 98, Karlsruhe (Ottenstein) / 3
The R/3 Integration Model
R/3Client / Server
ABAP
COControlling
AMFixed Assets
Mgmt.
PSProjectSystem
WFWorkflow
ISIndustry
Solutions
MMMaterials
Mgmt.
HRHuman
Resources
SDSales &
Distribution
PPProductionPlanning
QMQualityMgmt.
FIFinancial
Accounting
PMPlant
Maintenance
SAP AG 1998 O4 SAP TechEd 98, Karlsruhe (Ottenstein) / 4
Materials Management (MM) Overview
Internal and externalfinancial accounting
RequirementsPlanning
Internal procurementProduction
Invoiceverification
Sales and Distribution
Goodsreceipt
Postingchange
Master dataMaterialBatchesVendorG/L accountsCustomerStorage bins.
.
External procurementPurchasing
Invoicereceipt ?
Warehouse Management
InventoryInventory Management Management
Goodsissue
Page 3
SAP AG 1998 O4 SAP TechEd 98, Karlsruhe (Ottenstein) / 5
WM Overview
Warehouse control
Inventory control
Warehouse movements
Storage bin management
Shelf-life expiration date
Phys. inv.Phys. inv.
WMWarehouse
Management
SAP AG 1998 O4 SAP TechEd 98, Karlsruhe (Ottenstein) / 6
WM Overview Interface to other Systems
Remote data processing
Production supply
Delivery processing
Delivery
Quality Management
InventoryManagement
WMWarehouse
Management
Page 4
SAP AG 1998 O4 SAP TechEd 98, Karlsruhe (Ottenstein) / 7
Warehouse Structure in the System
High rack storage
Storage type 001
Picking area
Storage type 005
Storage type 004
Storage type 902
GR area
Storage type 902
GR area
Storage type 910
GI area
Storage type 910
GI area
Good receipt
Goods issue
Block storage
SAP AG 1998 O4 SAP TechEd 98, Karlsruhe (Ottenstein) / 8
Storage Bins and Quants
Bin type
High bins
Lower bins
Lower bins
Storage section
Fast-moving items
Slow-moving items
Page 5
SAP AG 1998 O4 SAP TechEd 98, Karlsruhe (Ottenstein) / 9
WM-System Hierarchy
Quants are Material / Batchdefined by: Stock category
Special stock PlantStorage unit number
Warehouse (complex) number
Storage bin
Quant
Storage type
SAP AG 1998 O4 SAP TechEd 98, Karlsruhe (Ottenstein) / 10
Warehouse number 002Warehouse number 001
Possible Structure with the WM System (1)
Plants
Storage types 001001 002002 001001 002002 003003
Storage locations 00880088 00880088
ExampleExample
00010001 00020002
Page 6
SAP AG 1998 O4 SAP TechEd 98, Karlsruhe (Ottenstein) / 11
Warehouse number 001
Possible Structure with the WM System (2)
Plants
Storage types 001001 002002 003003 004004
Storage locations 00880088 00880088
Example 2Example 2
00010001
00010001 00020002
SAP AG 1998 O4 SAP TechEd 98, Karlsruhe (Ottenstein) / 12
Several Storage Locations for WarehouseNumber
001001 002002 003003 004004
00010001 00020002 00030003
Plants
00010001
Storage locations
Warehouse number 001
Storage types
Page 7
SAP AG 1998 O4 SAP TechEd 98, Karlsruhe (Ottenstein) / 13
Staging area 3
Staging area 4
Staging area 5
Staging area 6
Staging area 7
Staging area 8
Staging area 9
Storage type
Picking area 1
Picking area 2
Picking area 3
Stagingarea 1
Staging area 2
Door 7
Door 6
Door 5
Door 4
Door 3
Door 2
Door 1
New Organization Structures in the Warehouse
SAP AG 1998 O4 SAP TechEd 98, Karlsruhe (Ottenstein) / 14
Contents
z
Overview about MM and WM
z
Interfaces WM-LSR and MM-MOB
z
Application Scenarios
z
Technical Aspects
z
Customizing (System Demo)
Page 8
SAP AG 1998 O4 SAP TechEd 98, Karlsruhe (Ottenstein) / 15
Link to Warehouse Control Units (LSR)
Administrative level
Physical control level
- Automatic storage retrieval system- Automatic fork lift system- Picking system, carousel...
IMIM SDSD
WMWM
WCUWCU
SAP AG 1998 O4 SAP TechEd 98, Karlsruhe (Ottenstein) / 16
WCU Functionality
WMWM
WCUWCU
Transfer order
Release reference number
Inventory bin location list
Cancellation requestfor transfer orders
Transfer order
Confirmation oftransfer orders
Cancellation of unconfirmed TO
Transfer requirements
(Un)blocking bins
Move storage units
Inventory count data
Page 9
SAP AG 1998 O4 SAP TechEd 98, Karlsruhe (Ottenstein) / 17
WCU with MDE
StockStock placement placementStockStock removal removal
ConnectionConnection to to scales scales Packaging of Packaging of delivery itemsdelivery items
BlockBlock bins bins in in warehousewarehouse
Inventory countingInventory counting
StockStock transfer transferinin warehouse warehouse
Replenishment Replenishment controlcontrol
IMIM SDSD
WMWM
WCUWCU
StockStock transfer transferPosting changePosting change
SAP AG 1998 O4 SAP TechEd 98, Karlsruhe (Ottenstein) / 18
Mobile Data Entry Functionality
Stock placement(production, ordering)
Stock transfer
Stock removal(cost center, ...)
Connection to scalesPackaging of delivery items
IM SD
Posting changes
Picking systemsdeliveries, picking quantities
Page 10
SAP AG 1998 O4 SAP TechEd 98, Karlsruhe (Ottenstein) / 19
Contents
z
Overview about MM and WM
z
Interfaces WM-LSR and MM-MOB
z
Application Scenarios
z
Technical Aspects
z
Customizing (System Demo)
SAP AG 1998 O4 SAP TechEd 98, Karlsruhe (Ottenstein) / 20
Scenario 1: Manual Warehouse
z Management of material stocks and storage binsz Creation of stock placement / removal transfer ordersz Stock placement / stock removal strategiesz Inventoryz Execution of physical movements via fork liftz TO in paper form as information medium
WM
GR area
GI area
HRS
Block storage
Page 11
SAP AG 1998 O4 SAP TechEd 98, Karlsruhe (Ottenstein) / 21
Scenario 2: Semi-Automated Warehouse
GR area
Rack storage
z
Management of material stocks and storage binsz
Creation of stock placement / removal transfer ordersz
Stock placement / removal strategiesz
Control of automated storage/retrieval systems AS/RS z
Control of material flowz
Optimization of resources depending on extension level
WM
WCU
GI area
SAP AG 1998 O4 SAP TechEd 98, Karlsruhe (Ottenstein) / 22
Scenario 3: Fully Automated Warehouse
GI area
GR area HRS
I
K
K
z
Management of material stocks and storage binsz
Creation of stock placement / removal transfer ordersz
Stock placement / removal strategiesz
Control of conveyor equipmentz
Control of material flowz
Optimization of resources
WM
WCU
Page 12
SAP AG 1998 O4 SAP TechEd 98, Karlsruhe (Ottenstein) / 23
Scenario 4: 'Blackbox'
GI area
GR area HRS
I
K
z
Management of stock totalsz
Creation of stock placement / removal transfer orders
z
Management of material stock figures and storage binsz
.....
WM
WCU
"Blackbox"
K
SAP AG 1998 O4 SAP TechEd 98, Karlsruhe (Ottenstein) / 24
= Customer Exit, customer IDoc
Scenario 5: Connect external warehouses
External warehouse management
GMtGMt
Pick
PackDel. Prod
MaterialsManagemt.
Sales &Distribution
ProductionPlanning
Materialmaster
MOB PDC ALEMOBC.E. C.E.
MAT
= standard IDoc
PDC = Plant data CollectionMOB = Mobile Data Comm.ALE = Application Link Enabling
GMt = Goods Mvt.Del = delivery doc.Pick = Picking dataPack = packing dataMAT = Material masterProd = Prod. Order
PDC
Page 13
SAP AG 1998 O4 SAP TechEd 98, Karlsruhe (Ottenstein) / 25
Example: Stock Placement Requirements
Container arrives
Goods receiptwith handheld device
Palletization, via conveyer into whse
Identification of palletand putaway in high rack type
SAP AG 1998 O4 SAP TechEd 98, Karlsruhe (Ottenstein) / 26
Solution 1: SAP Controls High Rack Storage1. Container arrives, scan PO # and send goods movement GM2. SAP posts Transfer order TO automatically, hereby destination bin loc. will be found (placement strategies...). TO sent to subsystem 3. Pallet identified at ID-point, TO confirmed and putaway
GR+TO
TO
Identif. Putaway
SAP
Sub
phys. GR area ( ID-point ) High Rack Storage
GM
conveyer
1
2
3
Confirm
TO confirmed
Page 14
SAP AG 1998 O4 SAP TechEd 98, Karlsruhe (Ottenstein) / 27
Solution 2: Subsystem Controls High Rack
GR+ 1stTO
TO Confirm
Identif.Putaway
Move SU
SAP
Sub
phys. GR area ID-pointSAP-managed
High Rack Storage
GM
conveyer
1. Container arrives, scan PO # and send goods movement GM2. SAP postings done automatically, TO sent to sub.3. Pallet identified at ID-point, TO confirmed and putaway4. After putaway, send IDoc 'Move Storage Unit' => 2nd TO
1
2
3 4
2nd TO
TO confirmed
SAP AG 1998 O4 SAP TechEd 98, Karlsruhe (Ottenstein) / 28
Solution 3: 'Black Box' Scenario
GR+ 1stTO
TO Confirm
Identif.Putaway
SAP
Sub
phys. GR area ID-pointSAP-managed
High Rack Storage
GM
conveyer
1. Container arrives, scan PO # and send goods movement GM2. SAP postings done automatically, TO sent to sub.3. Pallet identified at ID-point, TO confirmed and putaway
SAP only knows stocks on logical bins on ID-point.
1
2
3
TO confirmed
Page 15
SAP AG 1998 O4 SAP TechEd 98, Karlsruhe (Ottenstein) / 29
Contents
z
Overview about MM and WM
z
Interfaces WM-LSR and MM-MOB
z
Application Scenarios
z
Technical Aspects
z
Customizing (System Demo)
SAP AG 1998 O4 SAP TechEd 98, Karlsruhe (Ottenstein) / 30
Three Tier Architecture of R/3
Application Server A Application Server B
Frontend 2Frontend 1
Database Server
to externalSystems
to otherFrontends
to extrenalSystems l l l l l l
l l l
DatabaseLayer
PresentationLayer
ApplicationLayer
to otherFrontends
SAP Dispatcher A SAP Dispatcher B
Message Server
Central Database Manager
Operating System Services
non-SAPFrontend
ApplicationSAPGUI
RollArea
RequestQueue
SharedMemory(Roll Out
Area,Buffer,
etc.)
Database
Operating System Services
non-SAPFrontend
ApplicationSAPGUI
Operating System Services
non-SAPFrontend
ApplicationSAPGUI
WorkProcess
A2
WorkProcess
A1RollArea
WorkProcess
A3RollArea
WorkProcess
B1RollArea
WorkProcess
B2RollArea
RequestQueue
SharedMemory(Roll Out
Area,Buffer,etc.)
Page 16
SAP AG 1998 O4 SAP TechEd 98, Karlsruhe (Ottenstein) / 31
Application Link Enabling (ALE)R/3 System 1 R/3 System 2
ALE-enabled ApplicationInter-
MediateDocument
ALE-enabled Application
Inter-Mediate
Document
EDI-capableExternal
Application
EDIDocument
RFC
RFCEDI
Sub-system
External Application
Inter-Mediate
Document
EDI Subsystem
Extension of external application forconnection to ALE-enabled application:- mapping internal data structure to/from Intermediate Document- calling and receiving RFC using the RFC API
=
SAP AG 1998 O4 SAP TechEd 98, Karlsruhe (Ottenstein) / 32
ALE (Application Link Enabling)
ALE enables integrated configurations, in whichapplications are loosely coupled, i.e. asynchronouslyand not via a common database.
z Message-based Architecture z Business Scenariosz Communication Technologyz Tools z Methodology
ALE Infrastructure encompasses:
Page 17
SAP AG 1998 O4 SAP TechEd 98, Karlsruhe (Ottenstein) / 33
ALE Objectives
z
Scenarios: R/3 and R/3 R/2 and R/3 SAP and
non-SAP systems
z Support for differentapplication releases
z Integration of distributedapplications Consistency and
synchronization of distributeddata with respect to availabledatabase technology Support for the configuration
of distributed applications
SAP AG 1998 O4 SAP TechEd 98, Karlsruhe (Ottenstein) / 34
Different Structures on R/3, R/2 and Non-SAP
R/2 ,Non-SAP-System R/3
MARC
MARA
MARB
MARD
The data has to be converted to the other systems
MARD
MARC
MARM MEAN MSTA MOFF
MYNS MBEW MVKE MLAN MLGN
MKAL MFHM QMAT
MARA
MAKT
Page 18
SAP AG 1998 O4 SAP TechEd 98, Karlsruhe (Ottenstein) / 35
Sending Idocs from R/3 to non-SAP
R/3 System 1
ApplicationApplication
Application
&$// )81&7,21 ,1%281'B,'2&B352&(66
,1 %$&.*5281' 7$6. '(67,1$7,21
7$%/(6 ,'2&B&21752/ ,'2&B'$7$
Det. of recipient
FilterConversion
ALE
Comm.-IDocComm.-
IDoc
Communication
ALE Interface
MasterIDoc
Non-SAP System
Daten
Data
RFC Library
Translator
Comm.-IDocComm.-
IDoc
Daten
Data
SAP AG 1998 O4 SAP TechEd 98, Karlsruhe (Ottenstein) / 36
Sending Idocs from non-SAP to R/3Non-SAP System
Daten
Data
RFC Library
Translator
Comm.-IDocComm.-
IDoc
Daten
Data
5IF5F 5IF,QGLUHFW&DOO K5IF
,1%281'B,'2&B352&(66
([SRUWLQJ 7DEOHV
7UDQV,'
Comm.-IDocComm.-
IDoc
INBOUND_IDOC_PROCESS
FilterConversion
Workflow inputR/3 System 2
Applicationdata
Application Functions
Page 19
SAP AG 1998 O4 SAP TechEd 98, Karlsruhe (Ottenstein) / 37
Structure of an IDOCIDOC IDOC data structure (example)
HEADERHEADER
MM 11
ITEMITEM
MM 99999999
SUBITEMSUBITEM
OO 9999
ACCUMACCUM
MM 11
TEXTTEXT
OO 99999999
Datarecords
Sender Receiver MsgType IDOC-type StatusSender Receiver MsgType IDOC-type Status
HEADERHEADER xxxxxxxxxxxxxxxx
ITEMITEMSUBITEMSUBITEMSUBITEMSUBITEMTEXTTEXT
ITEMITEM
SUBITEMSUBITEMSUBITEMSUBITEM
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
xxxxxxxx
xxxxxxxx
xxxxxxxxxxxxxx
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
xxxxxxxx
xxxxxxxx
ACCUMACCUM xxxxxxxxxxxxxxxx
"Ready for processing" 16:22:34"Ready for processing" 16:22:34
"Successfully processed 16:22:42"Successfully processed 16:22:42
Control record
Status records
SAP AG 1998 O4 SAP TechEd 98, Karlsruhe (Ottenstein) / 38
Extensions to IDOCsz The customer may extend the IDOC structure by
inserting new segments
HEADERHEADER
MM 11
ITEMITEM
MM 99999999
SUBITEMSUBITEM
MM 9999
ACCUMACCUM
MM 11
TEXTTEXT
OO 99999999
EXT001EXT001
OO 1010
EXT002EXT002
OO 9999
Page 20
SAP AG 1998 O4 SAP TechEd 98, Karlsruhe (Ottenstein) / 39
Intermediate Document (IDOC)
z
SAP message standard, introduced for SAP-EDIz
Neutral data format (only character fields, ISO codesinstead of SAP codes)z
Tools available to get documented structure description machine readable structure description
z Only downwards compatible structure changesallowedz Customers extensions supported
SAP AG 1998 O4 SAP TechEd 98, Karlsruhe (Ottenstein) / 40
Communication via Remote Function Call
z Idocs are sent and received by R/3 using thetransactional Remote Function Call (tRFC).z The transactional RFC is a queued RFC to separate the
communication from the application.z A transactional RFC call is put in a queue on the
sending side. It stays in the queue until it has beensuccessfully communicated to the receiving system.
Page 21
SAP AG 1998 O4 SAP TechEd 98, Karlsruhe (Ottenstein) / 41
Architecure of the RFC Libraries
R/3Application
R/3 Application Server
RFC Protocol via TCP/IP
Call stubsfor
selectedfunctionmodules
(generated)
external system
Program, e.g. C
DynamicLink
Libraries
Local memoryExternalApplication
FB1 FBnFunction Library
RFCLIB- logon/off
- call/receive- table
handling
NIDLLvendorspecificTCP/IPsupport
CPICTLIBmaps CPI-C
to TCP/IP
CPI-C HandlerABAP/4Runtime RFC Interface
SAP AG 1998 O4 SAP TechEd 98, Karlsruhe (Ottenstein) / 42
SAP supported Network Products Rel. 3.1HSAP Communication to External SystemsCommunication to customer designed C programs
CPI-C RFC (Remote Function Call) RFC ClassCPI-C tlib
(*1)CPI-C slib
(*2)Synchronous
RFC(*3)
RFC loadbalancing
(*4)Pre-registered RFC
Server Pgm.(*4)
Asynchr. RFC(*4)
Transactional RFC(*4)
Interactive RFC(with external Pgm)
(*4)Librariesfor C++
IBM RS6000AIX 4.1.4
yes yes yes (*7)
HP 9000/700, 800HP-UX 10.20SNI RM 400/600SINIX5.43 B0051
(*5)
DEC AXPDigital UNIX 3.2C
Yes (*6) no yes (*6)
Sun SOLARIS 2.5 plannedOS/2 Warp 3.0WINDOWS 3.1/3.11 - no
WINDOWS 95NT 3.51/4.0 (Intel)AS/400OS/400 (*8)
yes yes
yes yes yes yes
yes yes
yes yes yes
yes yes yes
yes
yes yes
yes yes
(*7)
(*7)
(*7)(*7)yes yes yes yes
yes yes yes yesyesyesyes
yes
yes
yes
yes
yesyesyesyesyes
yes
yesyes
yes
yesyes
yesyesno
no no
no
no
yesyes
yesyes(*7)
(*7)
yes (*6)
yes (*6)
yes (*6)yes yes yes
yes (*6)
no nono no
planned
-
-
-
-
-
Page 22
SAP AG 1998 O4 SAP TechEd 98, Karlsruhe (Ottenstein) / 43
gwrd
SAPGateway
Call of an RFC-Client
R/3-System
FUNCTIONINBOUND_IDOC_PROCESSTABLES IDOC_CONTROL = EDI_DC IDOC_DATA = EDI_DD.
ABAP/4
RfcOpen (..)RfcCreateTransID(..,TID)ItCreate(..,tbl..)ItAppLine(..,tbl..)RfcIndirectCall(.,tbl,TID)RfcClose (..)librfc
...........
external RFC-Program
librfc
RFC-Interface
RFC Server Program RFC Client Program
SAP AG 1998 O4 SAP TechEd 98, Karlsruhe (Ottenstein) / 44
Call of an RFC-Server
R/3-System
CALL FUNCTIONINBOUND_IDOC_PROCESSIN BACKGROUND TASKDESTINATION TEST RFCTABLES IDOC_CONTROL = EDI_DC IDOC_DATA = EDI_DD.
ABAP/4
librfc
RFC Client Program
RFC-Interface
RfcAccept (..)RfcInstallTransactionControl (TID_check, TID_commit, TID_rollback, TID_confirm)RfcInstallFunction (..)RfcDispatch (..)INBOUND_IDOC_PROCESS (..){ ... RFC_Function RfcGetData (..tbl,..) ItGetLine(..,tbl) RfcSendData(..tbl,..)}RfcClose (..)....
TID_confirm(..){ /* delete TID */}
...........
RFC Server Program
external RFC-Program
librfc
SAPGateway
gwrd
Page 23
SAP AG 1998 O4 SAP TechEd 98, Karlsruhe (Ottenstein) / 45
Required Software
z
RFC library for the respective platformz
SAPGUI to access R/3 systemz
SAPGateway to start interface modulez
Maybe SAPRouter to ensure safe net access
SAP AG 1998 O4 SAP TechEd 98, Karlsruhe (Ottenstein) / 46
Contents
z
Overview about MM and WM
z
Interfaces WM-LSR and MM-MOB
z
Application Scenarios
z
Technical Aspects
z
Customizing (System Demo)