Ansicht
Dokumentation

The Distribution Center as a Separate Component ( RELNLE_45B_DEZLAGER )

The Distribution Center as a Separate Component ( RELNLE_45B_DEZLAGER )

ROGBILLS - Synchronize billing plans   PERFORM Short Reference  
This documentation is copyright by SAP AG.
SAP E-Book

Short text

The Distribution Center as a Separate Component

Description

As of release 4.5 it us possible to link up a Warehouse Management System (WMS) as a separate component to the SAP R/3 System, or to link the SAP R/3 Warehouse Management system with any arbitrary ERP system (Enterprise Resource Planning System). In both cases, the ERP system and the Warehouse Management system can run on separate computers.

This scenario is supported for the distribution center. The scenario describes a warehouse that is used primarily for the distribution of goods and is not linked up to a production center. The business transactions, including inventory management for quantities, are executed in the ERP system. All the processes required for goods receipt, storage, and distribution are executed at a separate warehouse level. Accordingly , this new function is divided up into two areas:

  • SAP R/3 as an ERP System
  • In the R/3 System, you define for each plant and storage location whether the warehouse activities are to take place in a separate Warehouse Management System. All information required for the WMS to execute the activities such as goods receipt or goods issue are transmitted to the WMS by a BAPI (Business Application Program Interface). This includes communication of the master data, such as customer, supplier, or material.

  • Inventory management and evaluation takes place in the ERP system. Functions such as the availability check (ATP), credit limit check, or checks in the foreign-trade area are also located here. In this way, it is ensured that the activities in WMS can be operated efficiently without further checks and that the warehouse itself can concentrate on the execution side.

  • As soon as the activities have been executed in the warehouse, the SAP R/3 System receives a verification from WMS. This then initiates the closing of the activity, which in turn normally leads to a stock posting in the SAP R/3 System.

  • SAP R/3 as a Warehouse Management System
  • The SAP R/3 System as a Warehouse Management System can receive inbound and outbound deliveries from any arbitrary ERP system. In the same way, master data can be communicated from the leading ERP system.

  • Incoming deliveries can be received in the warehouse on the basis of inbound deliveries that were reported from the ERP system to WMS. The delivery is checked and received in the warehouse. The goods movement is sent to the ERP system.

  • On the goods issue side, the Warehouse Management System performs all the functions required for shipping the goods. This includes picking, packing, loading, and creating the required shipping documents. The goods issue that then takes place is reported to the ERP system.

Effects on Customizing

For hints on the system settings in the ERP system, refer to the section Central Processing.

For notes on system settings in the WM system, refer to the section Decentralized Processing.

Planning

For release 4.5, we have completed the linking up of a distribution center. Warehouses that work near the production area can not yet work separately from the SAP R/3 System since production supply and goods receipt from production in release 4.5 is not yet supported for independent warehouses.

A connection from the warehouse as a separate component to Quality Management systems (QMS) is not yet supported in release 4.5.

In the scenario described above, a connection from a Transportation Management Systems (TMS) to release 4.5 is not yet provided either. Information on inbound and outbound activities is communicated through the inbound and outbound deliveries, respectively.

In release 4.5, a warehouse under SAP R/3 can communicate only with one ERP system. The service scenario where one warehouse works for sever al different companies is not yet supported.






BAL_S_LOG - Application Log: Log header data   rdisp/max_wprun_time - Maximum work process run time  
This documentation is copyright by SAP AG.

Length: 4815 Date: 20240603 Time: 042628     sap01-206 ( 104 ms )