|
SAP Retail and SiSu
Installations of SAP Retail generally are realised following one of two scenarios. Which one is selected depends on the organisation of the enterprise.
Scenario A
SAP-Retail is the central Merchandise Processing System, DEWAS III is the local component in the stores of independent retailers.
Scenario B
SAP-Retail is the central Merchandise Processing System, SiSu (Store Integration of Sub-Systems) controls the operative processes in the store , including the peripheral equipment.
For data exchange DEWAS III and SiSu process IDOCs directly from SAP. Converters resp. Data mapping systems are no longer required, thus reducing the risk of loss of data in either direction. The current new SAP-Architecture PDM (POS Data Management) is supported. The data models of SAP-Retail and DEWAS III /SiSu are matched, all special transactions that can occur in retail operations, like different packaging, displays, sets, calibrated goods, etc. are handled correctly.
Scenario A - DEWAS III as the local system
DEWAS III as a local merchandise system allows the store management total flexibility to organise the processes in the stores in the most efficient way.The concept of local data processing makes the store independent of central and network peak loads at the same time offloading the central SAP system.The local system fits seamlessly into the organisation, to the central system, its is transparent.All merchandise processing functions including stock keeping, are handled completely by DEWAS, leading to a clear separation of functions between central site and store.
Data exchange is handled via IDOCS generated by SAP-Retail. These include item data, suppliers up to EAN-linkages and price changes. Electronic delivery notes sent by SAP-Retail are processed in DEWAS. DEWAS III keeps item stock and evaluates all movements by sales and buying price.
Local systems like PDT’s scales, POS registers, label printers are controlled by DEWAS. DEWAS III generates orders that are sent to the central system or directly to a supplier.
DEWAS collects information on all merchandise movements by departments, groups or by item and passes this data on to SAP for further processing. In this way the decentralised stocks in the stores are available to SAP.
Scenario A has been realised for the following enterprises:
- Dänisches Bettenlager in over 600 stores
POS system POSition from Wincor Nixdorf
Label and poster printing
PDT’s for ordering and inventory
- Kloppenburg GmbH, over 150 Filialen
POS system Eurocash from Microdata
Label and poster printing
PDT’s for ordering and inventory
POS system POSition von Wincor Nixdorf
Label and poster printing
PDT’s for ordering and inventory
- SPAR Schweiz for independent retailers
POS system dStore from POS-Systemhaus, Austria
Label and poster printing
PDT’s for ordering and inventory
Attachment of scales
Scenario B - SiSu and Retail Store
All relevant merchandise processing functions central and distributed, are handled by the central SAP-system.
SiSu services as a frontend for optimising instore processes and to control the peripheral systems.
Since SiSu controls the locally attached systems, the data traffic to and from the central site can be unified and pre-processed before transmission.
This scenario has been realised for the following companies: POS system dStore from POS-Systemhaus
Label and poster printing
PDT’s for ordering and inventory
Attachment of scales
In the store SiSu handles price change schedules and activation, printing of shelf labels and posters and generates important reports fore the store management. In case the store is offline or the central system is not available through network problems etc. important functions like price changes, mark-downs etc. can be made locally via SiSu. This ensures that the store is still fully operational. Functions like ordering, recording miscellaneous movements and stock taking using PDT’s are supported by SiSu. Since SiSu has its own local database, a number of important functions can still be executed.
If the systems are online again, the consolidated data of the local changes is sent to the central SAP system.
SAP-IDOCS served by DEWAS III/ SiSu
- Data from SAP to DEWAS III/ SiSu
WPDTAX01 - VAT
WPDWGR01 - Sub-Departments / Departments
DEBMAS01 - Customers
CREMAS01/03 - Suppliers
WBBDLD02/03/04 - Items / Products
DELVRY01/03 - Electronic Delivery notes
WPDCUR01 - Exchange Rates
WPDBBY01 - Special Purchase Discounts
WALNOT01 - Promotion Pre-Orders
ZPROMOOUT - Initiation of Promotions
BOMMAT03 - Parts List
WVINVE02 - Counting Suggestions for Perpetual Stock
Taking
DESADVC - Electronic Delivery notes
INVOIC01 - Invoices
Z1RBSTK/Z1MBSTK - Back orders and Delivery notes
ZIELSUK/ZISBSTK - Goods receiving/Orders
- Data from SAP to DEWAS III / SiSu
WPUUMS01 - Sales Quantities, EAN based
WPUTAB01 - POS accounting / Tender Types
ACLREQ01 - Bookkeeping Data
WGSREQ02 - Purchase Orders
ZPROMOIN01 - Promotion Ordering
WALREQ01 - Promotions
WPUBON01 - Receipt Data
WPUWBW01 - Miscellaneous Movements / Stock
Corrections
WVINVE02 - Stock Consolidation / Stock Taking
POSDW/POSTR_CREATEMULTIPLE01
- Sales by receipt
- Miscellaneous Movements
- Cardtransactions
- Financial Data and Tender
- Monetary data from POS
- Scales Transactions Sales data
- Mark-Downs
|
