Vendor-Managed Inventory/Central Planning for Replenishment

The main goal of this scenario is to offer small subsidiaries/partners the planning and stock management expertise of the group and to create synergy effects with a centrally planned stock and transport situation.

Show Document Flow

Business Benefits

Increased visibility

Lower inventory levels

Optimized replenishment

Subsidary

Global Unit

Transfer historical sales data

Change and transfer demand plan data

Transfer of inventory and in-transit data

Generate purchase order

Create inbound delivery (ASN)

Create goods receipt for inbound delivery

Create inbound invoice

Generate demand plan

Send revised demand/budget plan to Subsidiary (via email or Internet)

Update demand plan

Generate central demand plan

Run supply chain planning

Generate customer order

Create outbound delivery (ASN)

Create outbound invoice

Business Benefits

Increased service level

Reduced supply risk

Less paperwork


Vendor-Managed Inventory/Central Planning for Replenishment SAP Business One at the subsidiaries / partners side is responsible for selling company products to end customers. The items which are sold most frequently are on stock at the subsidiaries (represented by SAP Business One). The sales order data and the actual stock situation (stock and stock in transit) are base for the demand planning forecast and Supply Network Planning in APO. Sales order data and actual stock data are being transferred daily from SAP Business One to SAP APO. In SAP APO demand planning, forecasting and Supply Network Planning (SNP) takes places. A transport order is being created in SAP APO and via CIF interface a sales order is generated in SAP R/3 for the material to be delivered to the subsidiaries / partners location. In SAP Business One a purchase order with refrence to the SAP R/3 sales order is being created. The process is being continued with creating a delivery in SAP R/3, which leads to an Advanced Shipping Notification (in form of an alert) in SAP Business One. An outgoing invoice in SAP R/3, which creates an incoming invoice with reference in SAP Business One closes the process. All changes on SAP R3 or SAP Business One documents lead to changes in the reference document. * = This business process is supported by Best Practices for SAP Business Suite. Best Practices for SAP Business Suite represent prepackaged business expertise in the form of methodology, documentation and reliable preconfiguration for SAP solutions. This helps you to start with a fully documented and reusable prototype for this scenario only days after you have installed the software. A prototype representing the results of a complete implementation project done up front and encapsulated in one single product that can rapidly turn into your productive solution. Best Practices for SAP Business Suite puts the power of SAP Business Suite in your hand.