Ansicht
Dokumentation
Vendor-Managed Inventory (VMI) ( RELNMM_PUR_40CVMI_ISR )
ROGBILLS - Synchronize billing plans BAL_S_LOG - Application Log: Log header dataThis documentation is copyright by SAP AG.
Short text
Vendor-Managed Inventory (VMI)
Description
- General Information on VMI
- Transferring Stock and Sales Data by EDI
- Receiving Stock and Sales Data by EDI
- Planning Replenishments for Customers
- Creating a Purchase Order for an Order Acknowledgment Received by EDI
General Information on EDI
Vendor-managed inventory involves vendors offering their customers the service of planning replenishments of vendor materials at the customer plant. The new functions allows VMI to be modeled from both a vendor and a customer point of view. VMI is typically used by manufacturers of consumer products that plan replenishments of their products at retailers.
The functions described here can be used independently of each other and are not restricted for use in VMI, but can be used in other scenarios.
Transferring Stock and Sales Data by EDI
A customer can, for example, transfer the stock data for certain materials to the manufacturer so that the manufacturer can gear their production to customer requirements and deliver the quantities required by the customer on time.
You use the message category PROACT to transfer information on stocks, quantities on-order, and sales by EDI to a recipient. You can display the information sent while the IDoc is being created or afterwards.
The sales data is taken from an information structure in the information system. You set up control profiles in Customizing to define which information structures are used and which key figures in the information structure are sent to the recipient.
Please read the IMG section: Profiles for Sending Stock/Sales data
Receiving Stock and Sales Data by EDI
A manufacturer would use this function, for example, to receive the current stock and sales data from a customer so that replenishments can then be planned for the customer.
Stock and sales data transferred using the message category PROACT can be received and processed by an R/3 system. The information received is processed as follows:
- Sales data
-
Sales data is adopted in information structure S130 and can be used for running a forecast or statistical analyses.
- Stock data
- Stock data is updated in the material master data used by Replenishment-it can be used to plan replenishments for customers, for example.
Please read the IMG section: Assign customer/vendor to sales organization data
Planning Replenishments for Customers
A vendor who has access to the current stock data of a customer would use this function, for example, to plan replenishments for the customer. This enables the vendor to use an automated method of determining exact customer requirements and delivering the goods as the customer needs them.
Replenishments are planned based on the replenishment stock data. The function determines the requirements of a specific customer and generates a sales order of the order type TAV as a follow-on document.
The sales order is transferred in the form of an order acknowledgment (message category ORDRSP with message variant VMI) by EDI to the customer. Before you can do this, an EDI partner profile must exist for the customer. The system generates the order acknowledgment for the sales order as a message of the type BAV0,for which you have to create the required condition records in the system. Be
Please read the IMG section: Output Determination Using the Condition Technique
Creating a Purchase Order for an Order Acknowledgment Received by EDI
A customer would use this function, for example, to receive information from their vendors about sales orders generated by the vendors in planning replenishments. The customer's R/3 system generates purchase orders for the order acknowledgment.
A purchase order is generated in the receiving system for order acknowledgments (message category ORDRSP with message variant VMI) received by EDI. If a purchase order cannot be generated (because the data is incomplete, for example), the system triggers a workflow.
Please read the IMG section: Assignment of vendor/customer to PORg data and plant
Damage caused to data by errors
Software/hardware requirements
Installation information
Effects on System Administration
Effects on Customizing
Effect on batch input
Changes to the Interface
Changes in procedure
Procedure for removing dataset errors
Dependent functions
Planning
Further notes
Fill RESBD Structure from EBP Component Structure Addresses (Business Address Services)
This documentation is copyright by SAP AG.
Length: 5801 Date: 20240520 Time: 204227 sap01-206 ( 99 ms )
