ISTech Support Forum

ISTech Support Forum
http://www.istechforum.com/YaBB.pl
Evo-ERP and DBA Classic >> Suggestions for Updates >> Sunrise 2005 Sructure (14 digits UCC code)
http://www.istechforum.com/YaBB.pl?num=1096291578

Message started by HB on 09/27/04 at 05:26:18

Title: Sunrise 2005 Sructure (14 digits UCC code)
Post by HB on 09/27/04 at 05:26:18

We have just been notified by one of our vendors that we must comply with the Sunrise 2005 Structure by January 1, 2005
This means that the current UPC code field in item setup must accommodate up to 14 digits ??? ???

Title: Re: Sunrise 2005 Sructure (14 digits UCC code)
Post by Lynn Pantic on 09/27/04 at 09:04:13

Helmut -

It looks to me that the Sunrise 2005 is more an imposition on retailers to be able to read the 14 digit UCC (European standard I think) rather than an imposition on US Manufacturers to be able to generate the 14 digit numbers. What exactly will you need to do to comply?

Title: Re: Sunrise 2005 Sructure (14 digits UCC code)
Post by HB on 09/27/04 at 10:48:48

the following is part of the email received:
-----------------------------------------------------------------------
• We will be prepared to accept inbound EDI Invoices
using a 12, 13, or 14-digit structure.
• Data structures that are less than 13-digits will be right justified and left zero padded.
The structure on our EDI Purchase Orders will be as follows:
Sunrise 2005 Structure Number Example EDI Format
UCC-12 (U.P.C. – A) 614141005277 061414100527

EAN/UCC-13 3439494949392 3439494949392
-----------------------------------------------------------------------

Does above make any sense to anyone?

Title: Re: Sunrise 2005 Sructure (14 digits UCC code)
Post by Lynn Pantic on 09/27/04 at 12:34:38

Is this one of your vendors or customers? If it is EDI, I presume customer. But I don't think the DBA EDI does anything with UPC per se, it uses either the DBA part number or Customer Cross-Reference which you may have defined as UPC.

Title: Re: Sunrise 2005 Sructure (14 digits UCC code)
Post by HB on 09/27/04 at 18:49:10

You are quite correct. We are actually importing a description that comprises SKU and UPC code that comes from a cross reference table (Access). The incoming EDI PO item line is compared with that external cross reference. So it looks like we do not really have to worry about anything else but to update this external table.

Thanks for your input