Promoción del diálogo entre los actores del proceso

Figure 23: Deployment

The deployment function in SNP plans the short-term distribution of the produced or procured products to the distribution centers. It determines when, and in what quantity, inventory and planned receipts can be deployed to distribution centers and vendor-managed inventory (VMI) accounts. If the ATD (available-to-deploy) quantity is insufficient to cover all demands, the fair share rules define the DC prioritization. These generate feasible, or even optimized, distribution plans with constraints (e.g. transportation capacities) and business rules (e.g. minimum cost approach or replenishment strategies), which can be transferred to ECC in the form of executable stock transport orders. Deployment generates optimized replenishment plans that take into account short-term changes on the supply or demand side as well as constraints, such as transportation and storage capacities.

There are several deployment strategies that can be used, such as fair share, push deployment, and pull-push deployment.

SCM230 Lesson: Supply Chain Planning

Figure 24: Transport Load Builder

The Transport Load Builder (TLB) is used to convert the results of the deployment run into SAP ECC stock transport orders or VMI sales orders that include several items for several products. The TLB ensures that:

The transport vehicles are filled to the maximum capacity,

No means of transport is dispatched that is not filled to at least minimum capacity.

The TLB uses transportation capacities efficiently by grouping together SCM stock transfers. The system checks the planned stock transfers against the minimum and maximum values defined in the system. If the planned stock transfers do not meet either the minimum or maximum requirements, the system activates an alert and the planner can readjust the TLB plan accordingly.

The TLB can also split stock transfers. It is a lot sizing procedure for stock transfers which can also be used as a preliminary step for SCM Transportation Planning and Vehicle Scheduling (TP/VS).

Unit 1: Overview of Supply Network Planning SCM230

Figure 25: Vendor-Managed Inventory (VMI)

VMI customers (both ship-to and sell-to customers) are created as locations in the supply network and connected to the supply chain through transportation lanes.

You create location product master records for the VMI location and define the planning parameters there.

The purpose of VMI is to include key customers in the supply chain plan. For VMI to function correctly, you need to know your customer's inventory and sales forecasts. VMI planning generates planned stock transfers between the DC and the customer location. Deployment and the Transport Load Builder build the transport loads and guarantee that the products are available, so that the VMI sales orders from SCM can be generated in ECC.

The data required for VMI planning, such as stock levels, stock on hand, and sales forecasts, is transferred by EDI messages and stored as persistent data in SCM. The important messages are EDI 852 (Product Activity Data) and EDI 830 (Forecast). SCM receives these messages in the form of a standardized PROACT IDOC to avoid data conversion and interpretation problems. These problems can also be resolved by EDI converters.

Depending on the agreement between the business partners in a VMI relationship, SCM can be set up to automatically create sales orders in SAP ECC using VMI, which minimizes the administrative work involved.

SCM230 Lesson: Supply Chain Planning

Figure 26: Integration between SCM and SAP ECC

The above graphic shows how transaction data is exchanged between SCM and the connected execution systems. These systems (for example, ECC systems) are known as online transaction processing (OLTP) systems.

You can transfer the results of Demand Planning as planned independent requirements to the OLTP systems, which is similar to the transfer from Flexible Planning or Sales and Operations Planning (SAP ECC) to Demand Management.

You can transfer the SNP planning results to the OLTP system as planned orders, purchase requisitions, and stock transport requisitions.

You can also transfer the PP/DS planning results to the OLTP system as planned orders, purchase requisitions, and stock transport requisitions. If you convert SNP planned orders into PP/DS planned orders, the planned orders are adjusted in the OLTP system. Planned orders can only be transferred to the OLTP system as production orders from PP/DS.

Deployment and the TLB confirm stock transport requisitions and can convert these requisitions into SAP ECC stock transport orders or VMI sales orders.

To configure the type of transfer you want, select APO → Supply Chain Planning

→ Supply Network Planning (SNP) → Basic Settings → Configure Transfer to OLTP Systems.

Unit 1: Overview of Supply Network Planning SCM230

Figure 27: Collaborative Planning in SCM

Collaborative planning includes the process by which different companies along the supply chain have access to shared information over the Internet (i.e.

across company boundaries) and work with the common goal of identifying and removing bottlenecks or date shifts as early as possible. Through collaborative planning, companies can exchange demand, procurement, and stock data with other companies.

You can define your own exception messages or alerts and integrate these alerts into the general alert management. If exceptions occur during planning, e-mail messages or fax messages can be generated automatically. SCM Collaborative Planning supports the Collaborative Planning Forecasting and Replenishment (CPFR) standard. A Web browser is sufficient for exchanging collaborative planning data.

SCM230 Lesson: Supply Chain Planning