SAP WM Interface To External Systems

Interfaces MM-MOB and WM-LSR
Michael Ottenstein
SAP AG
SAP AG 1998
O4 SAP TechEd 98, Karlsruhe (Ottenstein) / 1
Contents
Overview about MM and WM Interfaces WM-LSR and MM-MOB Application Scenarios Technical Aspects Customizing (System Demo)
SAP AG 1998
The R/3 Integration Model

SD
Sales & Distribution
FI
Financial Accounting
MM PP
Materials Mgmt. Production Planning
CO
Controlling
AM
R/3
Client / Server ABAP
HR
Human Resources
Fixed Assets Mgmt.
QM
Quality Mgmt. PM
PS
Project System
Plant Maintenance
WF
Workflow
IS
Industry Solutions
SAP AG 1998
Materials Management (MM) Overview

Requirements Planning External procurement Purchasing Internal procurement Production
Invoice verification
Goods receipt
Warehouse Management
Master data
Material Batches Vendor G/L accounts Customer Storage bins . .
Invoice receipt
Inventory Management ? Goods issue Posting change
Internal and external financial accounting

SAP AG 1998
Sales and Distribution
WM Overview
Shelf-life expiration date
Storage bin management
Phys. Phys. inv. inv.
WM
Inventory control
Warehouse control Warehouse movements

SAP AG 1998
WM Overview Interface to other Systems
Inventory Management
Production supply
WM
Delivery
Remote data processing
Delivery processing Quality Management

SAP AG 1998
Warehouse Structure in the System

Storage Storage type type 902 902 GR GR area area Good receipt Storage type 001
High rack storage Storage type 004
Block storage Storage Storage type type 910 910 GI GI area area Goods issue
SAP AG 1998
Storage type 005
Picking area
Storage Bins and Quants

Bin type
High bins
Lower bins Slow-moving items Lower bins Fast-moving items
Storage section
SAP AG 1998
WM-System Hierarchy
Warehouse (complex) number
Storage type
Storage bin
Quant
Quants are defined by: Material / Batch Stock category Special stock Plant Storage unit number
SAP AG 1998
Possible Structure with the WM System (1)

Example Example Plants
0001 0001
0002 0002
Storage locations
0088 0088
0088 0088
Warehouse number 001 Storage types 001 001 002 002
Warehouse number 002 001 001 002 002 003 003
SAP AG 1998
Possible Structure with the WM System (2)

Example Example 2 2 Plants
0001 0001
0002 0002
Storage locations
0088 0088
0088 0088
0001 0001
Warehouse number Storage types 001 001 002 002 003 003
001 004 004
SAP AG 1998
Several Storage Locations for Warehouse Number

Plants
0001 0001
Storage locations
0001 0001
0002 0002
0003 0003
Warehouse number Storage types 001 001 002 002
001 004 004
003 003
SAP AG 1998
New Organization Structures in the Warehouse

Storage type
Door 1
Staging area 4 Staging area 3
Door 4
Door 2
Staging area 1
Picking area 1
Staging area 5
Picking area 2
Staging area 6
Door 5
Picking area 3 Door 3

Staging area 2
Staging area 7
Staging area 8 Staging area 9
Door 6
Door 7
SAP AG 1998
Contents
SAP AG 1998
Link to Warehouse Control Units (LSR)
IM
SD WM
Administrative level
- Automatic storage retrieval system - Automatic fork lift system - Picking system, carousel...
WCU
Physical control level
SAP AG 1998
WCU Functionality
WM
Transfer order Release reference number Inventory bin location list Cancellation request for transfer orders Transfer order Move storage units Cancellation of unconfirmed TO
Confirmation of Transfer transfer orders requirements (Un)blocking bins Inventory count data
WCU
SAP AG 1998
WCU with MDE

Connection to scales Packaging of delivery items
IM
Stock placement Stock removal
SD
Replenishment control
Stock transfer Posting change
WM
Inventory counting
Stock transfer in warehouse
Block bins in warehouse
WCU
SAP AG 1998
Mobile Data Entry Functionality

Stock placement (production, ordering) Connection to scales Packaging of delivery items
Stock removal (cost center, ...)
IM
SD
Picking systems deliveries, picking quantities
Posting changes
Stock transfer
SAP AG 1998
Contents
SAP AG 1998
Scenario 1: Manual Warehouse

GR area HRS
GI area
Block storage
WM
Management of material stocks and storage bins Creation of stock placement / removal transfer orders Stock placement / stock removal strategies Inventory Execution of physical movements via fork lift TO in paper form as information medium
SAP AG 1998
Scenario 2: Semi-Automated Warehouse

GR area
Rack storage
GI area
WM
Management of material stocks and storage bins Creation of stock placement / removal transfer orders Stock placement / removal strategies Control of automated storage/retrieval systems AS/RS Control of material flow Optimization of resources depending on extension level
WCU
SAP AG 1998
Scenario 3: Fully Automated Warehouse

GR area HRS
GI area
I K
WM
Management of material stocks and storage bins Creation of stock placement / removal transfer orders Stock placement / removal strategies Control of conveyor equipment Control of material flow Optimization of resources
WCU
SAP AG 1998
Scenario 4: 'Blackbox'
GR area HRS "Blackbox"
GI area
I K
WM WCU
Management of stock totals Creation of stock placement / removal transfer orders Management of material stock figures and storage bins .....
SAP AG 1998
Scenario 5: Connect external warehouses

Materials Managemt. C.E. MOB Sales & Distribution MOB Production Planning C.E. PDC Material master ALE = standard IDoc = Customer Exit, customer IDoc PDC = Plant data Collection MOB = Mobile Data Comm. ALE = Application Link Enabling GMt = Goods Mvt. Del = delivery doc. Pick = Picking data Pack = packing data MAT = Material master Prod = Prod. Order
Pick GMt GMt Del. Pack Prod MAT
External warehouse management PDC
SAP AG 1998
Example: Stock Placement Requirements
Container arrives Goods receipt with handheld device
Palletization, via conveyer into whse
Identification of pallet and putaway in high rack type
SAP AG 1998
Solution 1: SAP Controls High Rack Storage

1. Container arrives, scan PO # and send goods movement GM 2. 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
phys.
GR area GR+TO GM 2
conveyer
( ID-point )
High Rack Storage TO confirmed Confirm
SAP
TO
Sub 1 Identif. 3 Putaway
SAP AG 1998
Solution 2: Subsystem Controls High Rack

1. Container arrives, scan PO # and send goods movement GM 2. SAP postings done automatically, TO sent to sub. 3. Pallet identified at ID-point, TO confirmed and putaway 4. After putaway, send IDoc 'Move Storage Unit' => 2nd TO
phys.
GR area 2 GR+ 1stTO GM
conveyer
ID-point High Rack Storage SAP-managed TO confirmed Confirm 2nd TO Move SU Putaway
SAP
TO
Sub 1 Identif. 3
SAP AG 1998
Solution 3: 'Black Box' Scenario

1. Container arrives, scan PO # and send goods movement GM 2. 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. phys. GR area 2 GR+ 1stTO GM Sub 1 Identif. 3
conveyer
ID-point High Rack Storage SAP-managed TO confirmed Confirm Putaway
SAP
TO
SAP AG 1998
Contents
SAP AG 1998
Three Tier Architecture of R/3

Operating System Services Operating System Services
to other Frontends non-SAP Frontend Application
Operating System Services

non-SAP Frontend Application
Presentation Layer
non-SAP Frontend Application
SAPGUI
SAPGUI
SAPGUI
to other Frontends
Frontend 1
Frontend 2
to extrenal Systems
Message Server
GGG GGG
to external Systems
Application Layer
Request Queue
GGG
SAP Dispatcher A
Work Process A1 Work Process A2 Work Process A3
SAP Dispatcher B
Work Process B1 Work Process B2
Request Queue
Shared Memory (Roll Out Area, Buffer, etc.)
Roll Area
Roll Area
Roll Area
Roll Area
Roll Area
Shared Memory (Roll Out Area, Buffer, etc.)
Application Server A
Application Server B
Database Server
Database Layer
Central Database Manager Database
SAP AG 1998
Application Link Enabling (ALE)

R/3 System 1 ALE-enabled Application
InterMediate Document
R/3 System 2 ALE-enabled Application
RFC
EDI Subsystem = EDI Subsystem

EDI Document
RFC
Extension of external application for connection to ALE-enabled application: - mapping internal data structure to/from Intermediate Document - calling and receiving RFC using the RFC API
EDI-capable External Application
External Application
SAP AG 1998
ALE (Application Link Enabling)

ALE enables integrated configurations, in which applications are loosely coupled, i.e. asynchronously and not via a common database. ALE Infrastructure encompasses:
Message-based Architecture Business Scenarios Communication Technology Tools Methodology
SAP AG 1998
ALE Objectives
Integration of distributed applications

T Consistency and
synchronization of distributed data with respect to available database technology
Scenarios:
T R/3 and R/3 T R/2 and R/3 T SAP and
non-SAP systems
T Support for the configuration

of distributed applications
Support for different application releases
SAP AG 1998
Different Structures on R/3, R/2 and Non-SAP

The data has to be converted to the other systems
R/2 , Non-SAP-System R/3
MARA
MARA
MAKT
MARM
MEAN
MSTA
MOFF
MARB MARC MARD
MYNS
MBEW
MVKE
MLAN
MLGN
MARC
MKAL MFHM QMAT
MARD
SAP AG 1998
Sending Idocs from R/3 to non-SAP

Application
R/3 System 1 Application Application
Master IDoc
ALE
Det. of recipient Filter Conversion
Communication
Comm.IDoc
Comm.IDoc
ALE Interface
&% &* *!# $$ # & %$ $% % % $ * %# *%
Non-SAP System
RFC Library
Daten
Daten
Comm.-
Data
Data
Comm.IDoc
IDoc
Translator
SAP AG 1998
Sending Idocs from non-SAP to R/3

Non-SAP System
Daten Daten Comm.-
Data
Comm.IDoc
IDoc
Data Translator RFC Library

#1.#. #1. 3/ 70.9, #1. &* *!# $$ 5479 3 %,- 08 %7,38
R/3 System 2
Workflow input
Application Functions
INBOUND_IDOC_PROCESS
Comm.-
Application data
Filter Conversion
Comm.IDoc
IDoc
SAP AG 1998
Structure of an IDOC
IDOC
Control record
Sender Sender Receiver Receiver MsgType MsgType IDOC-type IDOC-type Status Status
IDOC data structure (example)

HEADER HEADER M M 1 1
HEADER HEADER ITEM ITEM SUBITEM SUBITEM SUBITEM SUBITEM TEXT TEXT ITEM ITEM SUBITEM SUBITEM SUBITEM SUBITEM ACCUM ACCUM
xxxxxxxx xxxxxxxx xxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxx xxxx xxxx xxxx xxxx xxxxxxx xxxxxxx xxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxx xxxx xxxx xxxx xxxx xxxxxxxx xxxxxxxx
Data records
ITEM ITEM M 9999 M 9999
ACCUM ACCUM M M 1 1
Status records
"Ready "Ready for for processing" processing" "Successfully "Successfully processed processed 16:22:34 16:22:34 16:22:42 16:22:42
SUBITEM SUBITEM O O 99 99
TEXT TEXT O 9999 O 9999
SAP AG 1998
Extensions to IDOCs
The customer may extend the IDOC structure by inserting new segments
HEADER HEADER M M 1 1
EXT001 EXT001 O O 10 10
ITEM ITEM M M 9999 9999
ACCUM ACCUM M M 1 1
EXT002 EXT002 O O
SAP AG 1998
SUBITEM SUBITEM M M 99 99
TEXT TEXT O O 9999 9999
99 99
Intermediate Document (IDOC)

SAP message standard, introduced for SAP-EDI Neutral data format (only character fields, ISO codes instead of SAP codes) Tools available to get
T documented structure description T machine readable structure description
Only downwards compatible structure changes allowed Customers extensions supported
SAP AG 1998
Communication via Remote Function Call

Idocs are sent and received by R/3 using the transactional Remote Function Call (tRFC). The transactional RFC is a queued RFC to separate the communication from the application. A transactional RFC call is put in a queue on the sending side. It stays in the queue until it has been successfully communicated to the receiving system.
SAP AG 1998
Architecure of the RFC Libraries

External Application external system Local memory Program, e.g. C
Dynamic Link Libraries
Call stubs for selected function modules (generated)
RFCLIB
- logon/off - call/receive - table handling
CPICTLIB
maps CPI-C to TCP/IP
NIDLL
vendor specific TCP/IP support
RFC Protocol via TCP/IP
R/3 Application Server R/3 Application

SAP AG 1998
Function Library FB1
FBn
ABAP/4 Runtime
CPI-C Handler RFC Interface
SAP supported Network Products Rel. 3.1H

SAP Communication to External Systems
Communication to customer designed C programs
CPI-C
CPI-C tlib CPI-C slib Synchronous (*1) (*2) RFC (*3) IBM RS6000 AIX 4.1.4 HP 9000/700, 800 HP-UX 10.20 SNI RM 400/600 SINIX5.43 B0051 DEC AXP Digital UNIX 3.2C Sun SOLARIS 2.5 OS/2 Warp 3.0 WINDOWS 3.1/3.11 WINDOWS 95 NT 3.51/4.0 (Intel) AS/400 OS/400 (*8) RFC load balancing (*4)
RFC (Remote Function Call)

Pre-registered RFC Asynchr. RFC Transactional RFC Interactive RFC Server Pgm. (*4) (with external Pgm) (*4) (*4) (*4)
RFC Class
Libraries for C++
yes yes yes Yes (*6) yes yes no no yes
yes yes (*5) no yes yes no no yes
yes yes yes yes (*6) yes yes yes (*6) yes (*6) yes yes (*6)
yes yes yes yes yes yes yes yes yes yes
yes yes yes yes yes yes yes yes yes yes
(*7) (*7) (*7) (*7) (*7)
yes yes yes yes yes yes no yes yes yes
yes yes yes yes yes yes no yes yes no
yes
planned no no yes yes no
(*7) (*7)
yes (*6) planned
SAP AG 1998
Call of an RFC-Client
RFC Server Program
ABAP/4
FUNCTION INBOUND_IDOC_PROCESS TABLES IDOC_CONTROL = EDI_DC IDOC_DATA = EDI_DD.
RFC Client Program
...........
RFC-Interface gwrd
RfcOpen (..) RfcCreateTransID(..,TID) ItCreate(..,tbl..) ItAppLine(..,tbl..) RfcIndirectCall(.,tbl,TID) RfcClose (..)
librfc R/3-System
SAP Gateway
librfc
external RFC-Program
SAP AG 1998
Call of an RFC-Server
RFC Client Program
ABAP/4
CALL FUNCTION INBOUND_IDOC_PROCESS IN BACKGROUND TASK DESTINATION TEST RFC TABLES IDOC_CONTROL = EDI_DC IDOC_DATA = EDI_DD.
RFC Server Program

...........
RFC-Interface
gwrd
librfc
SAP Gateway
R/3-System
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 */ }
librfc
external RFC-Program
SAP AG 1998
Required Software
RFC library for the respective platform SAPGUI to access R/3 system SAPGateway to start interface module Maybe SAPRouter to ensure safe net access
SAP AG 1998
Contents
SAP AG 1998

SAP WM Interface To External Systems

Enviado por

Dados do documento

Título original

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

SAP WM Interface To External Systems

Enviado por

Direitos autorais:

Formatos disponíveis

Interfaces MM-MOB and WM-LSR

O4 SAP TechEd 98, Karlsruhe (Ottenstein) / 2

The R/3 Integration Model

Fixed Assets Mgmt.

O4 SAP TechEd 98, Karlsruhe (Ottenstein) / 3

Materials Management (MM) Overview

Inventory Management ? Goods issue Posting change

Internal and external financial accounting

Sales and Distribution

O4 SAP TechEd 98, Karlsruhe (Ottenstein) / 4

Shelf-life expiration date

Storage bin management

Phys. Phys. inv. inv.

Warehouse control Warehouse movements

WM Overview Interface to other Systems

Remote data processing

Delivery processing Quality Management

Warehouse Structure in the System

High rack storage Storage type 004

Storage type 005

Storage Bins and Quants

Lower bins Slow-moving items Lower bins Fast-moving items

O4 SAP TechEd 98, Karlsruhe (Ottenstein) / 9

Possible Structure with the WM System (1)

Warehouse number 001 Storage types 001 001 002 002

Warehouse number 002 001 001 002 002 003 003

O4 SAP TechEd 98, Karlsruhe (Ottenstein) / 10

Possible Structure with the WM System (2)

001 004 004

O4 SAP TechEd 98, Karlsruhe (Ottenstein) / 11

Several Storage Locations for Warehouse Number

Warehouse number Storage types 001 001 002 002

001 004 004

O4 SAP TechEd 98, Karlsruhe (Ottenstein) / 12

New Organization Structures in the Warehouse

Picking area 3 Door 3

Staging area 8 Staging area 9

O4 SAP TechEd 98, Karlsruhe (Ottenstein) / 14

Link to Warehouse Control Units (LSR)

Physical control level

O4 SAP TechEd 98, Karlsruhe (Ottenstein) / 15

O4 SAP TechEd 98, Karlsruhe (Ottenstein) / 16

WCU with MDE

Stock transfer Posting change

Stock transfer in warehouse

Block bins in warehouse

O4 SAP TechEd 98, Karlsruhe (Ottenstein) / 17

Mobile Data Entry Functionality

Stock removal (cost center, ...)

O4 SAP TechEd 98, Karlsruhe (Ottenstein) / 18

O4 SAP TechEd 98, Karlsruhe (Ottenstein) / 19

Scenario 1: Manual Warehouse

Scenario 2: Semi-Automated Warehouse

Scenario 3: Fully Automated Warehouse

Scenario 5: Connect external warehouses

Pick GMt GMt Del. Pack Prod MAT

External warehouse management PDC

O4 SAP TechEd 98, Karlsruhe (Ottenstein) / 24

Example: Stock Placement Requirements

Container arrives Goods receipt with handheld device

Palletization, via conveyer into whse

Identification of pallet and putaway in high rack type

O4 SAP TechEd 98, Karlsruhe (Ottenstein) / 25

(7) (7) (7) (7) (*7)