830 Planning Schedule with Release Capability
for Kroger / Peyton
Introduction to 830’s aka Forecasting
Our expectation is that by sharing this valuable information with you, and by working together we will be able to:
- Reduce cycle time
- Utilization of next day shipping
- Utilization of multiple ordering review days
- Utilization of VMI 852/855
- Utilization of the EDI Forecast 830
- Increase use of Efficient Order Quantities
Peyton's is currently using a new forecasting tool that will allow the vendor to
receive via EDI, a 17-week forecast of item movement, Kroger will send 13 week-forecast. This information will be communicated to you in the EDI 830 transaction. This new tool utilizes key historical and promotional plan factors such as display, retail price, advertised, and item seasonality, to create an item forecast. This forecast has proven to be very accurate in forecasting future item movement for items shipping from our
distribution centers.
Our expectation is that by sharing this valuable item information with you, and by
working together we will be able to reduce total cycle time durations, increase
service levels, and improve accuracy throughout the entire supply chain. Peyton
will work with selected companies to further improve the supply chains process,
which we firmly believe will create a win for both our companies. There is a
greater potential to increase sales and profits as a result of an improved in-stock
position.
EDI runs twice a day, 7 days a week, but we don't necessarily have data to send out all 7 days.
- Displays and bonus items are not transmitted. The bonus item forecasts are combined with the corresponding base item forecasts to transmit a single forecast on the base item.
- Process to run daily
- The Sunday night/Monday morning run will continue to contain all items for all EDI vendors. However, for other days, only the items whose forecast has changed in Chain Store (Procurement) will be sent to the vendors.
- Forecast to be in vendor cases, always rounded up to the next case.
- Data will be sent in either ca – cases or ea - eaches
- Forecast to be the value held in Chain Store rather than the value sent from RDF. This means that if a buyer changes a forecast, the vendor will see that change, even if no corresponding change is made in RDF.
7.Conversely, if a change is made in RDF, but the Chain Store forecast has been locked by the buyer, the vendor will not see that change (until the following weekend when all the lock switches are reset).PAIRED TRANSACTIONS
- The 852 and 830 are paired transactions.
- You must receive the 852 in order to get the 830. The 852 and the 830 must go to the same receiver.
- Because of the “same receiver” requirement the JIT# is used as the EDI cross-reference.
- It is similar to VMI in that the buying group must approve the relationship, the JIT# must be cross-referenced and the purchasing system flags must be set.
The TP ISA ID must be set up in Kroger Partner file.
Steps for 830 set up…
Confirm Request with division
- Division to provide:
Division number, Vendor name and number and any UPC corrections.
- The Vendor should provide this information to the division and to EDI:
TP Name, Start Date, TP ISA ID and ISA Qualifier, Contact Information.
OLP- JIT#:
- Many partners are already set up with a JIT# / ISA ID cross-reference.
- The vendor and the division need to confirm the relationship, ISA ID, JIT#, JIT# cross-reference and set the flags for OLP. Once the 830’s are sent you will need to confirm the first transmission back to the Division
The LIN Item Identification segment will contain:
- UPC with a “UA” Qualifier or GTIN with a “UK” if 5010
- Purchasers item code with a “PI” qualifier
The FST Forecast Schedule segment will contain:
- The total of SDQ (total forecast quantity for all weeks)
- The forecast start date (Sunday)
- The forecast end date
THE SDQ Destination Quantity segment will contain:
- Unit measure
- Facility D-U-N-S + 4
- 17 week forecast on each Item (Peyton)
13 week forecast on each Item (Kroger)
Page -1-10/22/2018