In a VMI relationship you send the vendor an 852 Product Activity Data document, which contains sales quantities and stock levels for items they supply to you. In return, the vendor sends you an 855 Acknowledgment (Inbound), from which your system creates an open purchase order.
The system processes an incoming VMI 855 as follows:
Creates an open purchase order in one of the following ways:
Uses the purchase order number supplied by the vendor. You should reserve a block of valid, unused Eclipse purchase order numbers for the vendor to assign to 855s.
Uses the next available purchase order number generated by Eclipse. You must have the Use Next Available PO# for VMI Orders option on the EDI Add'l Doc Info screen set to Yes to use this feature. The VMI transaction program then uses the next available purchase order number and populates the Order ID field on the purchase order Header tab, with the automatically generated number.
Checks the prices and product numbers on the 855 with those stored in your system.
If there are no discrepancies, the system sets the order status to Open.
If there are discrepancies, the system sets the order status to Bid and adds the order to the Remote Order Entry Review Queue, where you can view the error detail.
If your site is using Virtual Supplier and the Enable Auto-Routing On Creation Of Sales Order control maintenance record is set to Y for a branch, when the system receives an inbound 855 Acknowledgement it creates an entry in the review queue for each order generation. If no branches on the order are enabled for auto-routing, the system creates a single review queue entry for the order. In this scenario, the stocking branch must also be flagged in the Define Routing Vs. Sourcing control maintenance record.
The system adds any days set in the Freight Days field in Vendor Maintenance for the vendor to the ship date and the required dates on the purchase order.
See Also: