36

EDI Agenda EDI Communications with NAV The Standard 800 Series The 900 Series – Warehouse and Intercompany Transactions Vendor EDI The 200 Series – Freight

Embed Size (px)

Citation preview

EDI

Agenda• EDI Communications with NAV• The Standard 800 Series• The 900 Series – Warehouse and Intercompany Transactions• Vendor EDI• The 200 Series – Freight EDI• Less Frequently Used 800 Docs• Other Options• Hosted EDI• Supplier Point of Sale Analysis• Recent Trends

EDI Communications within NAV

• Who’s already using EDI?• EDI Options:

o Lanhamo Lanham + SPS Commerce – a

hosted solutiono 3rd Party Softwareo Other hosted service

providers (ex: GXS, Redtail, DataMasons)

Lanham• Pros:

• Eliminates the need for other translation tools• No more double entry of documents in multiple systems• The Lanham piece can be / has been updated with food specific

functionality• JF library and internal expertise continues to grow• Control resides with customer

• Cons: • Control resides with customer• Communication piece must be handled by a third party

» FTP scripts » Cleo Lexiom

• User interface could be more appealing

Lanham & JustFoodERP

• IB product offerings use the EDI solution built by Lanham & Associates as its core EDI platform.

• ANY EDI transaction can be mapped into the system

• Only specific transactions have functionality already built into the platform…

The Standard 800 Series

• 850 - Inbound Purchase Order – creates a NAV Sales Order document

• 875 - Inbound Purchase Order (Grocery) – creates a NAV Sales Order document

• 810 - Outbound Sales Invoice – sent from a NAV Posted Sales Invoice document

• 880 - Outbound Sales Invoice (Grocery) – sent from a NAV Posted Sales Invoice document

Watch Out…

• Cross References• EDIout (totaling) requirements• EDIout field requirements• Barcode cross references may not need UOM

references• Missing / Changing TP Specs• Change Management

The 900 Series – Warehousing & Intercompany Transactions

• 943 - Warehouse Stock Transfer Shipment Advice • Sent from a NAV Purchase Order or Transfer Order document • This transaction informs a location/warehouse to expect a receipt of product • Supports Warehouse Receipt documents • Can send up to 10 unique lot/serial no. combinations (with quantity per combination)

per document line• 944 - Warehouse Stock Transfer Receipt Advice

• Updates a NAV Purchase Order or Transfer Order document • This transaction updates the NAV document with the product information that was

actually received at the location/warehouse • Supports Lot and Serial No. tracking (eg. creates Item Tracking when required) • Supports Warehouse Receipt documents (eg. updates a warehouse receipt line if

required)

The 900 Series – Warehousing & Intercompany Transactions

• 940 - Warehouse Shipping Order • Sent from a NAV Sales Order or Transfer Order document • This transaction informs a location/warehouse to make a shipment of product

• 945 - Warehouse Shipping Advice • Updates a NAV Sales Order or Transfer Order • Is the response to the 940 transaction • This transaction updates the NAV document with the product information that was

actually shipped from the location/warehouse • Supports Lot and Serial No. tracking (eg. creates Item Tracking when required) • Supports Warehouse Shipment documents (eg. updates a warehouse shipment line if

required)

Watch Out…

• Warehouse Lot Requirements• One to many & Many to one relationships• Necessary Re-class

The 900 Series – Warehousing & Intercompany Transactions

• 947 - Warehouse Inventory Adjustment Advice • creates a NAV EDI Inventory Adjustment document • this transaction posts through as Physical Inventory

Journal lines in NAV • supports Lot and Serial No. tracking

• Other intercompany docs:• 850 - Inbound Purchase Order (Intercompany)

– creates a NAV Intercompany Sales Order document

• 850 - Outbound Purchase Order (Intercompany) – sent from a NAV Intercompany Purchase Order document

Vendor EDI

• 850 - Outbound Purchase Order • sent from a NAV Purchase Order document

• 810 - Inbound Vendor Invoice •Updates purchase order header and lines; primarily with qty to invoice and dollar amounts.

• 855 - Purchase Order Confirmation•Updates Purchase Order header and lines; primarily with quantity to receive, and shipment method details

The 200 Series – Freight EDI

• 204 - Motor Carrier Load Tender Transaction• Outbound document used to offer (tender) a shipment to a load carrier;

including scheduling, item and shipment details.• Generated en masse, using the data from the logistics run document.• Supporting details coming from warehouse shipments.

• 214 - Transportation Carrier Shipment Status• Inbound document, received from the load carrier to provide shippers with the

status of shipments, including planned appointment dates, times and locations• Updates details on the logistics run header and lines.

The 200 Series – Freight EDI

• 210 - Motor Carrier Freight Details and Invoice • Inbound document providing freight invoice details• Updates the NAV Freight Reconciliation document • Subsequently creating a purchase invoice that would apply

item charges to items on the referenced shipments• Limited functionality depending on variability of data

received

The 200 Series – Freight EDI

• Watchout..• Trouble with consistency and priority:• What document is being used to identify a shipment to your

carriers?• Is this the same document that is identified on the invoice?• How are your charges broken out on your freight invoices?

• By distance?• By weight?• By Pallet?

• How many different types of charges do you have?

Less Frequently Utilized 800s

• 856 - Advanced Shipment Notice (ASN) • Sent from a Bill of Lading document • Requires the E-Ship granule from Lanham & Associates

• 857 - Shipping and Billing Notice• provides the recipient of a shipment with data for both receipt planning and

payment generation.• The Trading Partner will receive information including Shipment level, Order

level, Pallet level, Carton level, and Item level information as well as the additional invoice detail.

• It is basically a way to reduce the redundancy of the 856 and 810 by combining them in one document.

Less Frequently Utilized 800s

• 812 - Credit/Debit Adjustment • creates a NAV EDI A/R Adjustment document • this transaction posts through to the Customer Ledger as sales journal entries

• 823 - Lockbox (eg. Bank Deposit) • creates a NAV Bank Deposit Worksheet • this transaction is processed through to a NAV Bank Deposit transaction

• 882 - Direct Store Delivery Summary Information • provides a summary of sales invoices without product details

• 810 Credit Memo• Requires additional granule (EDI Extended Doc Handling - 14000380)

Less Frequently Utilized 800s

• 867 - Product Transfer and Resale Report • Incorporated with new ‘Extended Sales’ functionality

• Creates a historical Posted Invoice document (without hitting customer or item ledgers)

• Calculates Rebates and Commissions just like regular Sales Order posting• If there is a Sold-By Customer No., and the Credit Sold-By Customer flag

is set, two sales journal lines are posted for the External Sale amount:• a. A Credit to the Sold-By Customer• b. An Invoice to the Bill-To Customer• Supports periodic Commission and Rebate calculations

Less Frequently Utilized 800s

• 820 (outbound)• An X12 820 Purchase Payment Advice is sent to a supplier when

payment is made, especially in the case of an EFT (electronic funds transfer).

• This document provides suppliers the ability to reconcile which invoices have been paid in full for any given payment.

• 846 (Inventory Advice outbound)• An X12 846 Inventory Advice allows suppliers to report their

product’s inventory information to their Trade Partner(s).

Less Frequently Utilized 800s

• 860 (PO change Request)• Used by the buyer to request a change to previously submitted purchase order

(850)• Creates a sales quote to hold change details pertaining to an order• Handles increased, decreased quantity transmissions (+- x), quantity replacements

and deletions

• Event Notifications• Built off of SMTP foundation in NAV• Sends email notifications on send or receipt of EDI docs with error • Saves manual check of EDI doc status • Can be used in other areas of NAV

Other Options?

• Vantage Point EDI• No document or transaction fees• Built on MS SQL server• .Net development tools

Other Options?

• RedTail EDI• Hosted Solution• Limited NAV integration experience ($ per additional doc)• Xml interface

Hosted EDI

• Problem: Resource dedication to EDI• EDI as a Business Service; things to consider:

• Which option is more expensive to purchase, implement and maintain?

• Which is easier/faster to implement?• Which offers the most reliable, responsive and timely post-

production support model?

• IB has partners with SPS commerce to offer a hosted EDI solution

Comparison of Models

The Value PropositionSupporting Retailer EDI demands

Tracking data to make sure it was sent or received by the VAN

Caring if a Retailer changes their specifications

Paying costs for dedicated EDI hardware

Paying external software and hardware maintenance fees

Contacting your customers’ EDI department to solve problems

Reading or understand an EDI specification

Planning for EDI version migrations

SPS Commerce

Retailer EDI

to Common

MAP

1234567

891011121314

15161718192021

22232425262728

APP MAP1

234?6789...2425

?2728`

Retailer #1EDI PO

1234

Retailer #2EDI PO345678

Retailer #3EDI PO345262728

ADAPTER

V4010VAN

V5010AS2

V5030FTP

?2728`

Biz Rules

NAV

V4010VAN

V5010AS2

V5030FTP Biz Rule Examples:

Item Cross ReferenceLocation Cross ReferenceAny turn-around data not stored in ERP

Webforms

• Webforms• An online way to send and receive human readable EDI documents

• Advantages• For documents that don’t “need” to be integrated with NAV can be compliant on Webforms• Backup system if documents can’t be viewed through NAV• For speedy compliancy requirements, Webforms can be up and running in 5 business days• Visibility and reporting remotely on inbound PO’s etc.

Webform PO

SPS – Supplier POS Analysis

• Trading Partner Intelligence• Based on receipt of the 852• Spend more time analyzing the business as opposed to

collecting data• Identify product performance across retailers• Identify sales trends• Predict orders• Assist in business and inventory plans

SPS – Supplier POS Analysis

SPS – Supplier POS Analysis

SPS – Supplier POS Analysis

• Consolidated views of consumer and product trends across retailers

• Automatic reports e-mailed to you to help you stay top of business trends

• Detailed item and store-level sell-through details available online from any location with Internet access

• Customizable views and item categories for use across all your retailers

• Quick and easy comparisons across retailers and categories

Recent Trends

• 856 – Spartan Stores • 870 Order Status Report –

Walgreens• Support for Read Only Documents• 879 Price Information– Dot Foods• iTrade & FoodLink

Q&A