Fred Meyer EDI - EDI824 for ASN’s
Advanced Shipment Notice (EDI856) is one of the optional EDI documents at Fred Meyer which can be used to notify packing information by the vendor/supplier to retailers.
Fred Meyer ASN requirements:
Here are the basic requirements for a vendor set up to use ASN (EDI856).
§ Vendor is able to receive Purchase Orders with SDQ (Store Destination Quantity) segments.
§ Ability to pack and label all cartons with a UCC-128 meeting our requirements.
§ Ability to send all Advanced Ship Notices prior to scheduling an appointment for unloading at the Distribution Center.
§ Ability to send ASN in Shipment, Order, Pack and Item hierarchy.
§ If more than one truckload is needed to ship purchase order complete, Vendor must have ability to send ASN for additional trucks within 24 hours of the first ASN sent.
Are ASNs Required for All Fred Meyer Orders? – ASN’s are only required for purchase orders with SDQ segments.
ASN cannot be used for an order without SDQ segments. ASN’s sent for non-SDQ purchase orders are rejected by our system.
Fred Meyer - EDI824 for ASN’s:
Application Advice (EDI824) is one of the mechanisms used to notify vendor of insufficient data or errors in inbound transmissions. Fred Meyer EDI is in the process of implementing EDI824 for ASN’s.
It is required to complete the EDI824 testing to enable the EDI824 flag for ASN’s at Fred Meyer.
Mapping Specifications:
EDI824 for ASN’s mapping specifications are the same as EDI824 for Invoices. So, it is NOT required to build new EDI824 maps for ASN’s. Please find the EDI824 mapping specifications
4010 version: http://edi.kroger.com/maps_fm/4010_824N(Non-Jewelry).pdf
5010 version: http://edi.kroger.com/maps_fm/5010_824_092810.pdf
OTI10 element signifies the original EDI transaction set ID. If OTI10 = 856, this indicates that the Application advise (EDI824) is for EDI856 (ASN) data.
How can you link the 824 to the 856 transaction?
Please note that, we send the EDI824 for ASN with reference to the purchase order number provided in the ASN. Purchase order number, Group Control# and Transaction control# are the key elements to link the EDI824 to the 856 transaction.
EDI824 element / EDI856 elementPurchase Order number / OTI03 / PRF01
Group Control# / OTI08 / GS06
Transaction set Control# / OTI09 / ST02
Example:
EDI824 data:
OTI*TR*TN*0012345678*****1727*17270001*856~
EDI856 Data:
GS*SH*11111111111*5032337598*20120426*1446*1727*X*005010VICS~
ST*856*17270001~
PRF*0012345678~
Error Messages:
TED01 / Error Code / Error Message / Error Cause012 / 3400F / ASN CAN NOT BE USED, EXPECTING PAPER PACKING SLIP. / ASN received from a vendor but order didn’t send with SDQ segments and Your ASN cannot be used.
Note: It is NOT required to resend the ASN in this case.
007 / 3401F / MISSING HIERARCHICAL LEVEL / Shipment level HL (Hierarchical level) is not present but order level HL is present.
Shipment, pack and Item level HL segments are present but order level HL segment is missing.
Shipment, Order and Item level HL segments are present but order level HL segment is missing.
Shipment, order and pack level HL segments are present but order level HL segment is missing
024 / 3402F / INVALID BSN SEGMENT / Shipment Identification number (BSN02) is equal to spaces ( Expecting nonblank)
007 / 3403F / Missing Purchase order Number / Purchase Order Number is equal to spaces. (Expecting nonblank).
007 / 3404F / Missing Store location number / Store location number is equal to spaces. (Expecting valid 5 digit store number).
007 / 3405F / Missing UCC/EAN-128 SSCC / Marks and Numbers (Used to identify a shipment) is equal to spaces.
007 / 3406F / Number of units shipped is missing / SN1 segment is not present.
007 / 3407F / Missing LIN segment at Item Level / LIN segment is missing at Item level.
007 / 3408F / Missing product ID / PRODUCT-UPC,PRODUCT-GTIN, PRODUCT-EAN,PRODUCT-SKU = SPACES
(Expecting at least one of UP/UK/EN/CB with associated number)
012 / 3409F / Order level contained multiple PRF segments / Multiple PRF (purchase order references) segments at order level.
012 / 3410F / Order Level contains multiple N1 segments / Multiple N1 (Name) segments at order level.
024 / 3411F / ORDER LEVEL N1 BY SEGMENT CONTAIN INVALID DATA / Multiple MAN segments at Pack level
012 / 3412F / Multiple LIN segment at item level / Multiple LIN segments at item level.
012 / 3413F / Item level LIN contained multiple SN1 segments / Item level LIN contained multiple SN1 segments.
006 / 3414F / Duplicate Carton ID / Duplicate value in MAN02 for different cartons
012 / 3423F / Invalid UPC/GTIN received on ASN / UPC does not exist in Fred Meyer system.
Fred Meyer expects an ASN as per purchase order. Please contact buyer if there are any changes in UPC/GTIN codes otherwise please resends the revised ASN as per purchase order.
012 / 3424F / Unordered UPC/GTIN received on ASN / UPC didn’t ordered but received on ASN
Fred Meyer expects an ASN as per purchase order. Please resend the revised ASN as per purchase order
012 / 3425F / Unordered Store received on ASN / Store not on the PO at all.
Fred Meyer expects an ASN as per purchase order. Please resend the revised ASN as per purchase order.
012 / 3426F / Unordered UPC/GTIN received for Store XXXXX / UPC didn’t order for store XXXXX but received on ASN.
Fred Meyer expects an ASN as per purchase order. Please resend the revised ASN as per purchase order.
012 / 3428F / Same Item at multiple item levels in a pack level. / Same item received at different item levels within the same Pack level
Fred Meyer EDI system skips the duplicate items with in the same pack level and it leads to the discrepancy in the quantity between ASN and the actual shipment
Note:
Original versus Replacement ASN –Fred Meyer prefers to receive one original ASN that is accurate and timely. If a correction is needed to the ASN, Replacement ASNs are allowed. Keep in mind, with a Replacement ASN, be sure you are using the same Shipment ID (BSN02) & Carton ID (MAN02) as the Original ASN
Contact Information:
If you have any questions or need additional information, Please contact